# SIBRO Insurance Broker Software > Manage prospects, policies, renewals, claims, accounts, teams and integrations with SIBRO — insurance broker software built for real operations. Public Ghost content for AI and LLM tooling. This file includes a bounded export of public pages first, then recent public posts. Append `.md` to any post or page URL to get the content in Markdown (for example, `/example-post.md`). ## Pages ### About SIBRO URL: https://sibro.app/about/ Last updated: 2026-09-18T16:02:39.000Z **Built because spreadsheets could no longer carry the work** > Insurance broking is a chain of responsibilities. A renewal must be followed up. An RFQ must reach multiple insurers. Quotes must be compared. Payments, policy delivery, claims, invoicing and reconciliation must all happen on time. > > As the number of customers grows, so does the complexity. Information spreads across spreadsheets, emails, documents and conversations. Ownership becomes unclear. Follow-ups become harder. Important actions can be missed. > > SIBRO was created to bring that work together. ## It started with one broker’s spreadsheet. In 2015, Vivek Stanley, Founder and CEO of Protracked, developed the first version of SIBRO to replace the Excel-based processes used in an insurance broker’s office. It began as a practical solution to a specific operational problem. As we worked more closely with brokers, we discovered that the same challenges appeared across the industry: disconnected information, repeated data entry, difficult follow-ups, limited visibility and growing dependence on individual team members. What began as an alternative to spreadsheets gradually evolved into a connected platform for managing the insurance broking lifecycle. - **2015** The first version was created inside a broker’s office. - **130+** Insurance broking firms now use SIBRO in everyday operations. ## One operation. Every stage connected. SIBRO connects the work that happens across a brokerage. Every stage remains connected to the customer and policy that created it, so teams can see what has happened, what is pending and who is responsible for the next action. - **Prospects** Requirements, ownership and follow-ups - **RFQs & quotes** Insurer coordination and comparisons - **Policies** Booking, issuance and delivery - **Service** Endorsements, instalments and documents - **Claims** Responsibility, status and pending actions - **Accounts** Invoicing, brokerage and reconciliation - **Renewals** Continuity, reminders and follow-through ## Designed to remove repetitive work. SIBRO includes practical tools such as email integration, reusable RFQ formats, configurable fields, document-assisted policy booking and rule-based pay-in and payout calculations. But the objective is not simply to add more features. It is to reduce repetitive work, make exceptions visible and help teams operate with greater clarity and professionalism. ## Built to adapt. No two insurance brokerages operate in exactly the same way. SIBRO is designed to accommodate different lines of business, branches, teams, partners, responsibilities and approval structures. Brokers can configure important parts of the system without losing the benefits of a structured platform. The core product continues to evolve through improvements made available to SIBRO customers. Specialised integrations or developments with committed delivery timelines are separately scoped when required. ## Technology should stay in the background. SIBRO is built on a modern, scalable technology foundation and deployed in environments designed for security, availability and growth. Technology matters—but users should not have to think about it during their working day. They should experience a system that is dependable, responsive and clear. ## Built by Protracked SIBRO is developed and supported by Protracked Software Solutions Private Limited. Our product, implementation and customer-success teams work closely with insurance brokers. This operational understanding shapes how SIBRO is designed, implemented and improved. [**About Protracked →**](https://protracked.in/about/?ref=sibro.app) --- ## See what changes when the work stays connected. We’ll demonstrate SIBRO around the workflows, teams and controls relevant to your brokerage—not through a generic sales presentation. [**Book a personalised demo →**](https://sibro.app/book-a-demo/) ### Roadmap URL: https://sibro.app/roadmap/ Last updated: 2026-09-09T16:28:32.000Z A transparent view of what we are improving across SIBRO. This page is organised by delivery stage and will evolve as priorities, regulations and customer needs change. ### Product Updates URL: https://sibro.app/updates/ Last updated: 2026-09-09T16:28:49.000Z Meaningful improvements across SIBRO, explained in practical terms. We will use this page to share product enhancements, workflow refinements and important platform changes. ### Insights URL: https://sibro.app/insights/ Last updated: 2026-09-09T18:08:13.000Z Practical perspectives on insurance-broking operations, dependable software and the workflows that connect them. ### Product URL: https://sibro.app/product/ Last updated: 2026-09-10T05:29:59.000Z _No content available._ ### Solutions URL: https://sibro.app/solutions/ Last updated: 2026-09-10T05:30:20.000Z _No content available._ ### Implementation URL: https://sibro.app/implementation/ Last updated: 2026-09-10T08:09:57.000Z _No content available._ ### Customers URL: https://sibro.app/customers/ Last updated: 2026-09-10T14:40:15.000Z _No content available._ ### Book a Demo URL: https://sibro.app/book-a-demo/ Last updated: 2026-09-10T15:51:20.000Z _No content available._ ## Posts ### IRDAI’s proposed reforms: Why brokers need to respond now URL: https://sibro.app/irdais-proposed-reforms-why-brokers-need-to-respond-now/ Last updated: 2026-10-10T07:25:14.000Z IRDAI’s proposed insurance distribution reforms could affect the income available to brokers to maintain trained staff, advise customers, service policies and assist with claims. The consultation paper, “Recalibrating Economics of Insurance Distribution,” proposes changes to commissions and who can distribute insurance. It raises an important question: will independent brokers be able to continue providing the support their customers need? These are consultation proposals, not final regulations. Brokers have an opportunity to explain their concerns and recommend changes. Please watch the video below as part of the wider discussion, and read the original consultation papers attached to this article. **Read the original consultation:** [Part 1: Distribution Reformspart 1 .pdf3 MBdownload-circle](https://sibro.app/content/files/2026/10/part-1-.pdf "Download") [Part 2: Distribution Costs and Commission StructurePART 2 .pdf2 MBdownload-circle](https://sibro.app/content/files/2026/10/PART-2-.pdf "Download") ## What is being proposed? The proposals include: - Bringing brokers, corporate agents, web aggregators and several other channels under a common **Insurance Distribution Entity (IDE)** framework. - Reducing initial capital requirements for IDEs to **₹10 lakh**, with additional financial requirements linked to business income. - Allowing insurance distributors to undertake non-insurance businesses, subject to applicable requirements. - Expanding access to multiple insurers and products, subject to the required knowledge and skills. - Introducing product-wise commission ceilings, with several limits for distribution entities lower than those for insurer-appointed agents and associates. __Examples of proposed maximum commissions (% of premium)__ | Insurance | Distribution entities (including brokers) | Agents and associates | | -------------------------------------- | ----------------------------------------- | --------------------- | | Individual health: first-time business | 15% | 20% | | Individual health: renewal / porting | 5% | 10% | | New-vehicle motor third-party | Nil | 2.5% | These are maximum limits, not guaranteed payments. ## Why should brokers be concerned? A broker’s work continues long after a policy is issued. Understanding risks, comparing coverage, explaining exclusions, arranging endorsements, supporting renewals and assisting with claims all require trained people and ongoing expenditure. The important question is whether the proposed remuneration adequately supports these responsibilities. The paper proposes lower commission ceilings for distributors that can offer policies from multiple insurers, and relatively higher ceilings for those restricted to an insurer’s products. **Should a distributor offering customers a wider choice receive a lower ceiling than one restricted to an insurer’s products?** Access to multiple insurers helps brokers compare cover and recommend suitable policies. Rules should address commission conflicts while protecting the value of independent advice. Large businesses with existing customer networks and income from other activities may be able to absorb low insurance margins more easily than firms that depend on insurance advice and service. If independent firms cannot cover their costs, customers could lose access to personal advice and claims support. ## Reform is necessary—but it must preserve advice and service Part 2 raises concerns about high payouts, payments between connected businesses and sales influenced by commissions. Brokers should support transparency and action against mis-selling. Reforms should also recognise the cost of responsible advice and continuing service, and ensure lower distribution costs deliver measurable benefits to customers. ## The larger risk we should not ignore Lower prices and more sellers may initially appear to increase competition. But if independent firms cannot survive on the available margins, business could eventually become concentrated among fewer, financially stronger firms. **Low prices today do not, by themselves, guarantee customer choice tomorrow.** This possible outcome should be assessed before the rules are finalised. The concern is whether the framework could unintentionally favour financial strength over independent advice. ## What should brokers ask for? Our submissions should seek: - Commission limits that recognise advice, servicing and claims-support costs. - Fair treatment of independent advice: explain why offering a choice of insurers should attract lower commission ceilings. - The same knowledge, customer-needs assessment and accountability requirements for everyone selling insurance. - Transparent payments between connected businesses, and safeguards against using other business income to unfairly exclude independent firms. - Digital marketplaces that compare policies fairly, disclose paid promotions and protect customer data. - Time to adapt, with checks on whether the changes weaken customer service or concentrate business among fewer firms. ## Please watch the video Please watch the video below as part of the wider discussion. Consider what these proposals could mean for your firm and the customers who rely on your advice and claims support. Use the original papers above to check the proposals and prepare your own response. [Watch the video](https://www.youtube.com/watch?v=Z18M9fJVKJw&ref=sibro.app) ## Put the impact on your firm on record Start with your main product categories. Compare your actual commission income with the proposed ceilings, separating first-time business, renewals and porting. Explain what that income supports—from advice and policy servicing to claims assistance. Share your findings with your association and submit specific recommendations. The paper specifies 25 October 2026 as the feedback deadline. Feedback can be submitted through [the consultation portal](https://iib.gov.in/dr?ref=sibro.app). The paper also provides an email route using the prescribed Excel template at **drfeedback@iib.gov.in**. Affordable insurance should come with meaningful choice and dependable support. Brokers need to explain what it takes to provide both. ### Report Claims from the Client Portal URL: https://sibro.app/report-claims-from-the-client-portal/ Last updated: 2026-10-05T14:46:01.000Z When a client needs to report a claim, the first details often arrive through a phone call, email or WhatsApp message. Your team then enters those details in SIBRO to begin processing it. Clients can now submit a claim intimation directly through your **Client Portal (Add On)**, bringing the details and available documents into SIBRO in one step. ### How it works If Claims is enabled in the Client Portal, your client can: 1. Click **Intimate Claim**. 2. Select the relevant policy from the policies they have access to. 3. Enter the available claim details. 4. Refer to the document checklist, if you have configured one, and attach any available documents. 5. Submit the intimation. Documents are optional, so clients can report a claim even when they do not have all the paperwork ready. SIBRO automatically records the claim intimation date. ### Your team can take it from there Once submitted, SIBRO creates a claim entry with the status **Claim Intimated** and emails the policy’s assigned claim processor. Your team can then review the details and continue processing the claim in SIBRO. As you update the claim, its status and details are reflected in the Client Portal, helping the client stay informed. This gives clients a simple way to report a claim and gives your team a record to start working from—with fewer details to copy across from messages. **Using the Client Portal Add On?** Make sure Claims is enabled, so your clients can access **Intimate Claim**. ### Reassigning Work When Users Resign URL: https://sibro.app/reassigning-work-when-users-resign/ Last updated: 2026-10-02T01:30:03.000Z An employee is leaving your firm next week. They have upcoming renewals to follow up, open claims to handle, and team members reporting to them. You know who will take over. Now those responsibilities need to move to the right people in SIBRO. With our latest enhancement, you can arrange this handover while recording the resignation. ### Start with the resignation When an employee resigns, we go to Settings → User → Employees, open their record, and mark the user as resigned. You can now select who takes over their responsibilities. For example, you may want one colleague to take over their renewals and another to handle their open claims. You can select separate replacements for the relevant roles, depending on the features enabled in your SIBRO. 0:00 /0:16 1× Recording an employee’s resignation and selecting replacements. The process is straightforward: 1. Open the employee’s record in S**ettings → User → Employees**. 2. Mark the user as resigned and enter the **resignation date**. 3. Select replacements for the responsibilities you want to hand over. 4. Review your selections and save. > Check the date and replacements carefully before saving. Once automatic reassignment has run, it cannot be automatically undone. ### You select the replacements. SIBRO updates the assignments. For the replacements you select, SIBRO handles the relevant changes: - **Business Owner and CRM:** Renewals after the resignation date move to the selected replacements. - **Claim Executive:** Responsibilities on active policies and open claims move to the replacement Claim Executive. - **Hierarchy head:** Users reporting to the resigned employee move to the replacement hierarchy head. So, in our example, the colleague taking over renewals can continue the follow-ups, while the colleague taking over claims becomes responsible for the active policies and open claims. If you record a past resignation date, reassignment runs immediately. If the employee is leaving on a future date, SIBRO schedules the handover to run automatically on that date. You can still adjust renewal assignments individually or through bulk updates if you want to distribute them across several colleagues. ### When a POSP leaves, the handover works similarly Open the POSP’s record in POSP User Master. Under General Status or Life Status, select Resigned for the relevant category. Enter the resignation date and select a replacement POSP. SIBRO then reassigns the relevant renewals after that date. 0:00 /0:20 1× ### SIBRO also checks new assignments After someone leaves, their name should not accidentally continue to be used for new business outside their active period. SIBRO now checks the relevant date when assigning a user: - **Prospects:** Tentative Start Date. - **Policies:** Policy Issued Date. - **Endorsements:** Endorsement Issued Date. If the selected user was not active on that date, SIBRO asks you to reassign the record before proceeding. 0:00 /0:08 1× SIBRO prevents assignments outside the user’s active period. ### Their history stays. Their ongoing work moves forward. Valid historical business remains attributed to the original user. The handover updates the relevant ongoing responsibilities, and reassignment changes are recorded in the audit trail. Record the resignation, select the replacements, and let your team continue the work with clear responsibility. For help using this enhancement, contact support. ### How Shrinithi scaled policy booking beyond 2,000 documents a day with AI URL: https://sibro.app/shrinithi-scaled-policy-booking-with-ai/ Last updated: 2026-09-18T06:31:23.000Z A year ago, increasing policy volumes created a straightforward but expensive challenge for Shrinithi Insurance Broking: every new policy document required more manual data entry. External data-entry support typically cost between ₹7 and ₹12 per policy document. One employee could enter approximately 70 to 90 policies in a working day. When volumes increased, the firm offered its team additional earning opportunities to continue the work from home after office hours. The arrangement helped clear immediate backlogs, but it was difficult to scale. Higher business volumes meant more manual work, more overtime and a greater risk of policy booking being delayed. This was the operational problem that led SIBRO to introduce AI-assisted policy data entry. ## The constraint was not employee effort The data-entry team was already working hard. The limitation came from the nature of the process. For every policy, someone had to open the document, read its contents and manually enter information into the appropriate fields. Even an experienced employee could process only a limited number of documents each day. At 70 to 90 policies per employee, a sudden increase of several hundred policies created an immediate capacity problem. The firm could add more people or ask the existing team to work longer—but both options made every additional policy more expensive to process. > The real question was not “How can the team type faster?” It was “How much of this work actually requires a person?” ## Introducing AI-assisted policy booking SIBRO introduced AI-based optical character recognition and data extraction primarily to address Shrinithi’s challenge. When a policy document is uploaded, the system reads the document and extracts the information it can identify. Instead of manually typing every available field, the data-entry team reviews the extracted information and handles the details that still require human judgement. Today, AI performs approximately 90% of the policy entry. The team focuses on the remaining exceptions, including: - Salesperson or business-owner information that is not present in the policy document - Internal information that cannot be inferred from the document - Values that do not match an available master or dropdown option - Unclear, missing or unusually formatted information - Records that require verification before the policy can be completed This changes the role of the employee. The person is no longer responsible for reproducing the entire document inside the system. Instead, the employee checks the result, completes the missing context and resolves exceptions. ## From 70–90 policies per person to days exceeding 2,000 Shrinithi now has days on which it books more than 2,000 policies. The total data-entry team consists of four people. Under the earlier fully manual process, four employees working at the reported rate of 70 to 90 policies each would represent a daily capacity of roughly 280 to 360 policies. Processing 2,000 policies would have required substantially more people, longer working hours or a backlog extending across several days. With AI handling most document-based entry, the same team can support approximately five to six times more overall volume. There is no longer a recurring need to offer after-hours data-entry work simply to keep pace with normal business growth. ## Understanding the cost correctly Previously, data-entry support cost approximately ₹7 to ₹12 for each policy document. SIBRO’s AI usage charge is ₹1 per document. That does not mean the broker’s complete processing cost is only ₹1\. The four-person team remains essential for reviewing the AI output, adding internal information and resolving exceptions. The more meaningful comparison is this: - The repetitive document-reading and typing component now costs ₹1 per policy for AI usage. - Approximately 90% of the entry is handled by AI. - The existing team concentrates on the smaller portion that requires human involvement. - The same team supports five to six times more business volume. - Additional volume no longer requires a proportional increase in data-entry staffing or overtime. The benefit comes from combining inexpensive automated extraction with focused human review—not from attempting to remove people from the process entirely. ## Why exception-based work scales better Traditional automation is often presented as replacing a complete job. In practice, insurance documents contain too many variations for that to be the most useful objective. Some information is consistently available and can be extracted automatically. Other information belongs to the broker’s internal process. Certain documents will always contain unusual formats, incomplete values or details that cannot be matched confidently. A more practical operating model is: 1. Let AI complete the predictable, document-based work. 2. Identify information that is missing or uncertain. 3. Present those exceptions to an employee. 4. Let the employee apply business context and judgement. 5. Use the completed record in the rest of the policy, accounts, servicing and renewal workflow. This approach gives the organisation the speed of automation without losing human control over the final policy record. ## What Shrinithi’s experience demonstrates The most important outcome is not simply that policy documents are processed faster. It is that policy volume and data-entry effort no longer have to increase at the same rate. Shrinithi can now handle days exceeding 2,000 policy bookings with a four-person data-entry team. AI completes most of the repetitive work, while employees deal with the information and exceptions that genuinely require their attention. For Shrinithi, AI was not introduced as a general technology experiment. It was introduced to solve a specific operating constraint—and its value is visible in the volume the same team can now support. [See how AI-assisted policy booking could work for your team →](https://sibro.app/book-a-demo/) ### What actually happens during a 15-day SIBRO implementation URL: https://sibro.app/what-actually-happens-during-a-15-day-sibro-implementation/ Last updated: 2026-09-18T06:31:28.000Z Buying insurance broker software is only the beginning. The real change happens when branches, users, data and everyday workflows begin moving into the system. SIBRO implementation normally takes around 15–20 working days for the core platform. We meet online for approximately one hour at a consistent time, work through one operational area at a time and use real business data wherever practical. The objective is not merely to demonstrate screens. By the end of the programme, the platform should be configured around the broking firm’s workflow and the team should have practised the work it will perform after go-live. ## Preparation begins before implementation We discuss the broking firm’s branches, teams, products and present workflows before the software is purchased. This helps align expectations and identify important operational priorities early. SIBRO has developed through more than ten years of continuous improvement and experience with over 130 insurance brokers. Most standard requirements are already available. Implementation is therefore usually about configuring the platform, moving real work into it and helping users develop confidence—not building the core system from the beginning. ## Why we use short daily sessions A single long training programme can introduce many features, but users rarely retain them without practice. Short daily sessions allow the team to understand one workflow, configure it, try it with real records and bring questions into the next discussion. The sequence can change according to the firm’s priorities, but a typical 15-session plan is: 1. **Essential administration:** branches, users, roles, access and basic masters. 2. **Upcoming policies:** prospects, renewals, follow-ups and pending work. 3. **Converted policies:** policy booking, issuance, documents and delivery. 4. **Pay-in rules:** supported brokerage and pay-in calculations. 5. **OCR and AI prompts:** reading policy documents and reviewing extracted information. 6. **Endorsements:** policy changes and servicing follow-ups. 7. **Instalments:** instalment-based life insurance policies. 8. **Invoicing and reconciliation:** invoices, insurer statements and differences. 9. **Pay-out auto-calculation:** partner payout rules where applicable. 10. **Pay-out processing:** reviewing and processing partner payouts. 11. **Emailing:** supported email communication from workflows. 12. **Claims:** stages, responsibility, documents and follow-ups. 13. **Declarations:** declaration workflows where applicable. 14. **RFQ and quote comparison:** collecting quotations and preparing comparisons. 15. **Reports:** operational, financial and management reporting. If the team needs additional practice, we can leave a short gap between sessions. Areas that do not apply to the firm can be replaced or reordered. ## Implementation is shared work ### What the SIBRO team does - Guide the implementation sessions - Help configure masters, workflows and controls - Explain useful practices and identify process gaps - Support data verification and issue resolution ### What the broking firm does - Bring the appropriate users and real business data - Make decisions about access, responsibilities and workflow - Practise each area between sessions - Learn how to use SIBRO settings for future changes > A successful implementation is not something a software vendor does to a broking firm. It is a working programme completed with the people who will use and administer the system. ## Customisation without rebuilding the product Different firms use different terminology, responsibilities and approval paths. During implementation, authorised users can configure many lists, fields, roles and workflows around the organisation’s way of working. These settings can also be changed later. A growing firm should not need a software development project every time it introduces a branch, changes an internal responsibility or improves a workflow. ## What happens after the first 20 days? Core onboarding may be completed within 15–20 days, but operational adoption continues after go-live. During the first few months, real usage exposes incomplete data, process mistakes, reconciliation differences and areas where users need more training. These are not necessarily signs of a failed implementation. They are often the issues that were already present but were difficult to see. By approximately three to four months, the objective is to have corrected recurring mistakes, improved processes, repeated training where necessary and made SIBRO part of everyday operations. ## Timelines for add-ons Partner/POSP, Customer and Employee Benefits portals usually require around 20 days, along with feedback sessions before go-live. Insurer and TPA integrations generally take longer—often two to three months—because access, specifications, testing and approvals depend on external organisations as well as the SIBRO team. ## Questions to answer before starting - Who will own the implementation internally? - Which branches and users should be configured first? - What data is ready to migrate or import? - Which workflows are highest priority? - Can the relevant employees attend and practise consistently? - Who will become the internal SIBRO administrator? Clear answers make the daily sessions more productive and help the firm move from software setup to confident use. [Discuss your SIBRO implementation plan →](https://sibro.app/book-a-demo/) ### Auto-fill insurer proposal forms from SIBRO URL: https://sibro.app/auto-fill-insurer-proposal-forms-from-sibro/ Last updated: 2026-09-27T05:05:45.000Z When an insurer requires a proposal form, you can prepare it from the details already entered in SIBRO. For a configured fillable PDF template, SIBRO fills the mapped fields and gives you a draft to review. You can correct the form before saving and downloading it. ## Create a proposal from an upcoming policy 1. Go to Policies > Upcoming and open the relevant policy. 2. Select Create Proposal. This option appears when a proposal template is connected to that policy. If more than one template is available, choose the one you need. 3. Review the PDF that SIBRO has filled. Add or correct any details in the form as needed. 4. Save and download the completed proposal. SIBRO also attaches the final file to the prospect's Proposal Attachment section. You can return to the proposal later to edit or download it, or restart it when you need a fresh copy. Always check the filled details and the insurer's requirements before submitting the form. ## Set up your insurer's form An administrator first needs to add the insurer's fillable PDF at Settings > Templates > Proposal. Give the template a name, select the insurer and applicable policies, and upload the PDF. Then map its fillable fields to the corresponding standard or custom fields in SIBRO. This is a one-time setup for each template; once connected, the team can create proposals from matching upcoming policies. This feature applies to insurer forms set up as fillable PDF templates. If Create Proposal is missing for a policy, check whether the appropriate template has been added and linked to that policy and insurer. ### Why insurance broker software must follow the policy lifecycle URL: https://sibro.app/why-insurance-broker-software-must-follow-the-policy-lifecycle/ Last updated: 2026-09-18T06:31:34.000Z A policy does not begin when it is booked, and the work does not end when the document is delivered. For an insurance broking team, one piece of business can move through an enquiry, follow-ups, quotations, payment, policy issuance, endorsements, claims, reconciliation and renewal. Each stage creates information that the next person needs. When those stages sit in separate spreadsheets, inboxes and folders, the team has to rebuild the story at every hand-off. The problem is not simply duplicate data entry. It is the gradual loss of context. ## What gets lost between disconnected tools? Consider a customer approaching a broker for an employee compensation policy. The relationship team records the requirement, an operations employee collects quotations, accounts confirms the payment, another user books the policy and a servicing employee later handles an endorsement. If each person maintains a separate record, ordinary questions become difficult: - Which requirement and quotation led to this policy? - Has the premium been received and matched? - Which documents have already been shared with the customer? - Who owns the pending endorsement or claim follow-up? - What brokerage was expected, received or still pending? - When should the next renewal conversation begin? People can usually find the answers eventually. The cost is the time spent searching, checking with colleagues and recreating information that the organisation already had. ## A connected policy lifecycle ### 1\. Begin with the customer and the opportunity The first record should capture information that remains useful later: the customer and contacts, insurance requirement, policy type, renewal or start date, available documents and the person responsible for the next action. When a prospect becomes business, this information should move forward instead of being typed again. ### 2\. Keep quotation decisions connected A quotation is more than a PDF attachment. It records the insurers approached, terms received, comparisons made and the option selected by the customer. Connecting this stage to policy booking preserves the reason behind the transaction and reduces repeated work. ### 3\. Treat policy delivery as the beginning of service After issuance, the same policy may have instalments, endorsements, declarations, document requests and other service activity. These should remain part of the policy history, with ownership and the next action visible. ### 4\. Make claims a managed workflow A claim develops over time. Documents arrive in stages, insurers and TPAs respond, surveyors may be involved, and customers need updates. A structured workflow shows the current stage, responsible person, pending requirement and follow-up history. ### 5\. Connect operational work with accounts Premium, invoices, brokerage, rewards and partner payouts should trace back to the policy that created them. This gives the accounts team the operational context needed to investigate differences instead of merely recording totals. It also makes reconciliation more useful. A difference can be traced to a missing policy, incorrect reference, pay-in rule, short receipt or genuine collection issue. ### 6\. Bring the renewal back to the beginning As the policy approaches expiry, the system should create or surface the next renewal opportunity with the existing customer, policy and servicing context intact. The team can start earlier and see what was renewed, lost or remains pending. ## Disconnected versus connected work **In disconnected work:** each department maintains its own version, follow-ups depend on memory, documents are searched for repeatedly and reporting becomes a separate collection exercise. **In connected work:** each stage adds to one operational history, the next action has an owner, financial differences can be investigated in context and management reports come from the same records used by the team. > The goal is not to put every activity on one screen. It is to make sure every person can see the information and next action required for their part of the journey. ## A practical checklist for broking firms When reviewing your present software or process, ask: - Does information move from prospect to policy without re-entry? - Can users trace quotations and customer decisions? - Are endorsements, claims and communication connected to the policy? - Can accounts investigate brokerage differences using policy context? - Does every pending activity have a visible owner and follow-up date? - Does the renewal begin with the previous policy history already available? At SIBRO, this lifecycle principle guides product development: understand how a broking firm actually works, preserve the context created at every stage and make the next action easier to see. [See how SIBRO connects the policy lifecycle →](https://sibro.app/book-a-demo/) ### Make renewal communication easier to configure and complete URL: https://sibro.app/more-flexible-renewal-communication-and-reporting/ Last updated: 2026-09-11T19:25:35.000Z Renewal follow-up works better when the message, previous policy and customer context travel together. SIBRO now gives broking teams more control over renewal communication and reduces the need to locate last year’s document separately. ## What changed - Policy-renewal SMS messages can use the newer configurable SMS settings. - The previous policy document can be included automatically in renewal communication. - The communication remains connected to the renewal workflow and its follow-up history. ## Why this matters A renewal reminder is more useful when the broking firm can control the wording and the recipient has the context needed to respond. Attaching the previous policy saves the servicing team from searching for the document and helps the customer or insurer review the expiring cover. Keeping the communication inside the workflow also gives the team a clearer record of what was sent and when the next action is due. ## Availability Message templates, document inclusion and delivery channels depend on the communication settings enabled for your organisation. ### Policy Snapshot Reports URL: https://sibro.app/policy-snapshot-reports/ Last updated: 2026-09-10T17:57:13.000Z Sometimes a team needs a policy-level answer without opening several screens or building a large report. WHAT IS ROLLING OUT Policy Snapshot Reports bring important policy, servicing and financial context into a concise view for review and follow-up. WHY IT HELPS Relationship, operations and management users can understand the current position of a policy faster. A useful snapshot can also support internal reviews and customer conversations without exposing every operational field in the system. STATUS Rolling out progressively. The information shown will depend on the policy type, available data and the reporting access assigned to the user. ### Review policy documents with more context in Approval Pending URL: https://sibro.app/a-clearer-approval-pending-workflow/ Last updated: 2026-09-11T15:14:40.000Z Approval Pending is not simply a yes-or-no queue. A reviewer needs the source document, the identity of the submitting user and enough context to decide whether the case is ready to become a policy record. SIBRO now brings more of that information and the related review actions into the Approval Pending workflow. ## What changed - Authorised users can download the source document directly from Approval Pending. - Direct policy bookings can show who submitted the case. - Approval-pending information can be downloaded for review and follow-up. - Policy documents received through approved email workflows can enter a structured review queue. - Import and validation checks help reviewers identify incomplete or unsuitable records earlier. ## Why this matters A reviewer should not have to ask a colleague to resend the document or explain where the case came from. Keeping the document, submitter and validation context together makes responsibility clearer and shortens the path to a decision. Managers also gain a more useful view of work that has entered SIBRO but is not yet ready to become a final policy record. ## Availability Document access, email intake and approval actions follow the roles and workflows configured for your organisation. ### From one claims notification to flexible workflow email templates URL: https://sibro.app/from-one-claims-notification-to-flexible-workflow-email-templates/ Last updated: 2026-09-18T06:31:39.000Z Some of the most useful product improvements begin with a small operational request. For Securus Insurance Brokers, the starting point was straightforward: when a claims query was raised, could SIBRO notify the customer directly from that workflow? The request was not simply for another email button. The real need was to make customer communication part of the work—triggered at the right stage, connected to the relevant record and visible to the team. ## Step 1: Notify the customer from a claims query SIBRO introduced a **Notify Customer** action at the Claims Query stage. The servicing team could communicate without leaving the claim, preparing a separate email and then recording what had been sent. This solved the immediate requirement and created a clearer history of customer communication. ## Step 2: The same need appeared elsewhere After the claims notification was released, other broking firms began asking for similar actions at more points in their workflows. - Notify the customer when policy documents are ready. - Communicate while processing an endorsement. - Send the appropriate message during other servicing activities. SIBRO added notifications at additional stages in subsequent updates. What began as one claims feature was becoming a common communication capability. ## Step 3: Similar workflows needed different messages Wider usage exposed a more important requirement: different broking firms did not want to communicate in the same way. One firm wanted its own email content at the **Policy Document to Client** stage. The wording reflected its service approach and was not intended to be shared with other brokers. At around the same time, another firm had prepared emails for approximately 30 endorsement scenarios. It wanted users to select the right message from a dropdown at the **Endorsement Request to Insurer** stage—and was willing to share those scenarios. Both requests were reasonable, but a single hard-coded email could not support them. Adding a separate software condition for every new scenario would also become difficult to maintain. ## Step 4: Move from fixed emails to a configurable master The underlying requirement was not “add more emails.” It was “let each broking firm control the communication available at each workflow stage.” SIBRO therefore moved towards master-based email templates. A firm can define multiple templates, connect them to the appropriate workflow and let users choose the relevant message while completing their work. This approach allows a team to: - Maintain approved and consistent communication across branches. - Create different templates for different service scenarios. - Update wording without changing the underlying software workflow. - Keep firm-specific templates private. - Reuse suitable shared scenarios where appropriate. ## How one request became a reusable capability 1. **Claims query:** Securus requested customer notification inside the workflow. 2. **More stages:** other firms requested notifications for policy documents and endorsements. 3. **Different content:** firms needed private wording and multiple reusable scenarios. 4. **Product capability:** master-based templates gave each organisation control. > Continuous improvement does not mean accepting every request as a separate custom feature. It means understanding the repeated need behind those requests and improving the product at the right level. ## What other broking firms can learn **Put communication inside the workflow.** Users are more likely to send the right message when it is available at the point where the work happens. **Standardise without becoming rigid.** Approved templates improve consistency, while multiple scenarios preserve the flexibility needed for real customer and insurer situations. **Give administrators control.** Communication changes more frequently than core software. Allowing authorised users to maintain templates reduces unnecessary dependency on development. **Look for the capability behind the request.** The best solution may serve many workflows and organisations without forcing all of them to work identically. The Securus story reflects how SIBRO has grown over time: solve the immediate operational problem, observe how different firms use the improvement, and then build enough flexibility for the next requirement. [Talk to us about your servicing and communication workflows →](https://sibro.app/book-a-demo/) ### Require a clear disposition before a claim moves forward URL: https://sibro.app/july-2026-claims-and-commission-control-improvements/ Last updated: 2026-09-11T15:14:36.000Z A claim can move through several stages while still leaving one important question unanswered: what happened at the previous stage? SIBRO claim workflows can now require a disposition before work moves forward, giving the servicing team a clearer record of the outcome and next action. ## What changed - Selected claim stages can require a disposition before the user proceeds. - The requirement can be aligned with the claim process followed by the broking firm. - The recorded outcome becomes part of the claim’s follow-up history. ## Why this matters A claim rarely becomes difficult because every piece of information is missing. More often, the owner, outcome or next action is unclear. A required disposition asks the user to close that gap while the interaction is still familiar. This creates a more dependable hand-off between claim executives, processors and managers. Someone reviewing the claim later can see not only that a stage changed, but also the operational reason for moving forward. ## Availability Required dispositions are configurable. The stages, options and access available to users depend on the claims workflow followed by your organisation. ### Proposal Form Autofill URL: https://sibro.app/proposal-form-autofill/ Last updated: 2026-09-10T17:56:22.000Z Proposal forms often repeat details that have already been captured during prospecting, quotation or customer onboarding. WHAT IS ROLLING OUT Proposal Form Autofill carries available customer, contact and policy information into the proposal workflow. Users remain able to review, complete and correct the form before it is finalised. WHY IT HELPS The operations team spends less time copying the same information between screens. Reuse also reduces avoidable spelling and transcription errors, while keeping the original SIBRO record connected to the proposal. STATUS Rolling out progressively. Autofill coverage depends on the proposal format, policy type and quality of the information already available. ### Improved Partner Portal experience URL: https://sibro.app/improved-partner-portal-experience/ Last updated: 2026-09-10T17:54:54.000Z Partners and POSPs need a simpler view of their own business without being exposed to the complexity of the internal SIBRO workspace. WHAT IS ROLLING OUT A more focused Partner Portal with clearer navigation, useful policy access and better visibility of relevant reconciled payout statements. Relationship managers also gain clearer POSP context in connected workflows. WHY IT HELPS Partners can answer common policy and payout questions with less back-and-forth. Relationship managers can see who is connected to the case, while the broking firm continues to control access and the information made available. STATUS Rolling out progressively. Portal modules and data access depend on the organisation’s configuration and permissions. ### How Unilight made commission recovery faster with exception-based reconciliation URL: https://sibro.app/how-unilight-made-commission-recovery-faster-with-exception-based-reconciliation/ Last updated: 2026-09-18T06:31:46.000Z Unrecovered brokerage is rarely visible as one obvious mistake. It is usually hidden across insurer statements, policy records, invoices and follow-up notes. At Unilight Reinsurance Brokers, a seven-person team was spending weeks matching insurer statements and following up on differences. The work was important, but too much effort went into checking transactions that were already correct. ## The difficulty with line-by-line reconciliation In a manual process, every entry looks like work. The team compares policy numbers, premium, expected brokerage and the amount received—often across files with different formats and references. As volume grows: - A missing or differently formatted policy number can prevent a match. - A short receipt can remain hidden inside a large statement. - Employees may repeat checks because there is no shared verification history. - Genuine collection issues compete for attention with correctly paid transactions. The result is more than slow reconciliation. Skilled employees spend their time proving that normal transactions are correct instead of recovering what is genuinely pending. ## Changing the unit of work With SIBRO, reconciliation became exception-based. Rather than presenting the entire insurer statement as a task list, the process separates matched records from items that require attention. The team can then focus on exceptions such as: - Expected brokerage not received - Short or excess receipts - Transactions without a matching policy - Policy or invoice reference differences - Amounts that require a rule or data correction The underlying policy, premium and financial context remains available, so an exception can be investigated rather than merely listed. ## Before and after ### Before - Seven people involved in reconciliation activity - Weeks spent matching statements and following up - Correct and incorrect transactions reviewed together - More effort spent searching than resolving ### After introducing exception-based reconciliation - The activity could be handled by three people - The team concentrated on genuine differences - Commission recovery became faster - The cost of recovering pending commission reduced > Automation created value by removing already-matched transactions from the work queue—not by removing the judgement required to resolve an exception. ## A better exception queue asks better questions For every difference, the team should be able to ask: 1. Was the expected brokerage actually received? 2. Does the insurer’s reference match the policy or invoice in another format? 3. Is the difference caused by booking data, a pay-in rule or an actual short payment? 4. Who owns the insurer follow-up? 5. What was the last action, and what remains pending? This turns reconciliation from a periodic spreadsheet exercise into an operational control. ## What other broking firms can learn **Reconcile continuously.** A difference is easier to understand when it is found close to the transaction date. **Work from exceptions.** A long insurer statement is not a useful task list. A shorter, prioritised list of differences is. **Connect accounts to operations.** Brokerage and receipts are easier to investigate when the underlying policy, premium, branch and owner are visible. **Use recurring errors to improve the process.** Reconciliation can expose incorrect rules, incomplete booking, missing references and training gaps—not only payment gaps. ## Keeping the result realistic Every implementation is different. Results depend on transaction volume, statement quality, available references and the discipline with which the team follows the process. The Unilight outcome should therefore be understood in its own operational context. The broader principle remains useful: when software removes correctly matched work from the queue, people can concentrate on recovering what is genuinely pending. [See how SIBRO handles pay-in reconciliation →](https://sibro.app/book-a-demo/) ### Stop unsuitable and duplicate records before policy booking URL: https://sibro.app/safer-faster-policy-and-document-processing/ Last updated: 2026-09-11T15:14:32.000Z Errors are easier to prevent before a record enters the policy workflow than to correct after the same information has reached servicing, accounts and reporting. SIBRO now applies clearer safeguards during imports and quote selection so unsuitable or duplicate records can be identified earlier. ## What changed - Quote selection can prevent the use of insurer companies that are not live for the intended workflow. - Validation and duplicate checks can stop avoidable records before they enter the operational queue. - Import workflows can omit POSP name and category when those values should not be carried into the receiving record. ## Why this matters A value that is acceptable in one workflow may be inappropriate in another. Likewise, an insurer or product should not be selectable merely because it exists in a master if it is not active for that transaction. Applying these checks at the point of entry reduces downstream clean-up. Operations teams receive a more dependable queue, accounts teams work with cleaner records and reports are less likely to reproduce avoidable data problems. ## Availability The safeguards depend on the insurer, product, import and access configuration used by each organisation. ### Faster renewal quotations with prefilled details URL: https://sibro.app/faster-renewal-quotations-with-prefilled-details/ Last updated: 2026-09-10T17:54:44.000Z Renewal quotations often begin with information SIBRO already knows. Re-entering the customer, risk and expiring-policy details slows down a time-sensitive process. WHAT IS ROLLING OUT Renewal quotation flows that prefill relevant information from the expiring policy while allowing the user to review and change it before sending a request. WHY IT HELPS Teams start with better context, reduce repetitive typing and are less likely to omit an important detail. The existing policy remains the reference, while the renewal case records the new request, quote and decision. STATUS Rolling out progressively. Available fields depend on the policy type and the information recorded in the previous policy. ### Process employee exits faster with bulk termination imports URL: https://sibro.app/better-portals-for-partners-and-employee-benefits/ Last updated: 2026-09-11T15:14:11.000Z Employee exits can create a significant servicing workload for teams managing group policies, particularly when several members must be removed at the same time. SIBRO Employee Benefits now supports bulk termination imports, allowing authorised users to process multiple member terminations through a structured workflow. ## What changed - Termination details for multiple members can be prepared and imported together. - The information enters a consistent administrative workflow instead of being processed one member at a time. - Teams can review exceptions before completing the activity. ## Why this matters For a small group, individual updates may be manageable. For a larger employer, a batch of exits can mean repetitive entry, slower endorsement preparation and a greater chance of missing a member. A bulk import reduces repeated work while preserving the controls needed to review the submitted information. The employee-benefits team can spend more time resolving exceptions and less time reproducing the same administrative action. ## Availability This capability is available through the Employee Benefits solution. The required format and approval process depend on the workflow configured for the group-policy team. ### Add the right business context to operational reports URL: https://sibro.app/september-2026-clearer-reporting-and-validation/ Last updated: 2026-09-11T15:14:07.000Z An operational report is useful only when the person reading it can identify the business and take the next action without repeatedly opening another screen. SIBRO reports now carry more of the references that operations, accounts and management teams need during daily review. ## What changed - Upcoming reports can include POS codes. - Converted-policy reports can include the invoice date. - Business Statements have an additional filtering option to help teams narrow the records under review. ## Why this matters A POS code helps the team connect upcoming business with the appropriate partner context. The invoice date helps accounts users understand where a converted policy sits in the billing process. Better filters make it easier to move from a large Business Statement to the smaller set of transactions that needs attention. These fields reduce cross-checking. The user can review, filter and export the information with more of its business context intact. ## Who benefits The improvements are relevant to renewal teams, policy operations, accounts and managers who depend on exported reports for follow-up and review. Available columns and filters may depend on the report and configuration used by your organisation. ### Dedicated Quotes Workspace URL: https://sibro.app/dedicated-quotes-workspace/ Last updated: 2026-09-10T17:54:34.000Z Quotation work deserves a workspace of its own. It involves requests, insurer selection, documents, reminders, multiple responses and a final comparison—not just a single field on a prospect. WHAT WE ARE PLANNING A dedicated Quotes Workspace that brings open requests, received quotes, pending responses, comparisons and follow-up into one focused area. WHY IT COULD HELP Operations teams could see what is waiting and what requires action without opening every prospect. Relationship teams would have a clearer picture of available options, while management could understand quotation turnaround and pending workload. STATUS Planned next. We expect the workspace to build on SIBRO’s existing RFQ and quote-comparison workflows. ### Give partners a clearer view of reconciled payouts URL: https://sibro.app/august-2026-faster-document-handling-and-payout-visibility/ Last updated: 2026-09-11T15:14:03.000Z Partners should not have to contact the broking team every time they need to understand a policy or a payout. The SIBRO Partner Portal can now give authorised users access to relevant policy information and reconciled payout statements through their connected workflows. ## What changed - Partners can view the policy information made available to their role. - Reconciled payout statements can be accessed through the portal. - Access continues to follow the permissions and partner relationships configured by the broking firm. ## Why this matters A payout figure is useful only when the partner can understand the business behind it. Connecting the statement with the relevant policy information makes the calculation easier to review and explain. It also reduces repetitive requests to operations and accounts teams. Instead of repeatedly sending the same policy and payout information, the broking firm can make an approved view available through the portal. ## Availability This capability is available through the Partner Portal add-on and depends on the payout, reconciliation and access configuration used by the organisation. ### Email-to-SIBRO policy document intake URL: https://sibro.app/email-to-sibro-policy-document-intake/ Last updated: 2026-09-10T17:54:25.000Z Policy documents frequently arrive in a shared mailbox before they reach SIBRO. Downloading and uploading each attachment adds a repetitive step and creates room for missed cases. WHAT WE ARE PLANNING Allow authorised mailboxes to forward or submit policy documents for structured intake into SIBRO. Incoming files could enter an approval queue where a user reviews the document and links or creates the appropriate record. WHY IT COULD HELP Teams can keep email as a receiving channel while moving the actual work into a visible, controlled queue. This should reduce manual uploads and make unprocessed documents easier to identify. STATUS Planned next. Sender controls, duplicate handling, security and review rules will be part of the rollout. ### Compare multiple quote options from the same insurer branch URL: https://sibro.app/july-2026-stronger-quote-comparison-and-renewals/ Last updated: 2026-09-11T15:13:10.000Z Quotation work does not always follow a one-insurer, one-quote pattern. The same insurer branch may offer several options with different premiums, covers, deductibles or commercial terms. SIBRO now lets a broking team record multiple quotations from the same insurer branch and decide which premium values should appear in the comparison shared with the customer. ## What changed - Users can retain more than one quotation from the same insurer branch. - The team can choose the premium values that should be shown in the comparison. - Alternative options remain connected to the same requirement instead of being maintained in separate files. ## Why this matters Previously, alternative terms from the same insurer could force the team to maintain additional notes or rebuild the comparison outside the workflow. That made it harder to preserve the complete decision history. Keeping the options together gives operations and relationship teams a clearer view of what was offered. It also helps the customer compare relevant alternatives without being distracted by fields that do not apply to the decision. ## Who benefits This is most useful for teams handling commercial or complex policies where an insurer may provide several structures for the same requirement. Available options may depend on the quotation workflow configured for your organisation. ### Clearer AI/OCR document-review results URL: https://sibro.app/clearer-ai-ocr-document-review-results/ Last updated: 2026-09-10T17:54:16.000Z Automated document reading is useful only when a reviewer can understand what was found, what is uncertain and what needs attention. WHAT WE ARE PLANNING A clearer review experience for AI- and OCR-assisted document processing. Results would separate confidently extracted values from validation warnings, missing information and suggested next actions. WHY IT COULD HELP Users could review a document faster without treating automation as unquestionable. Clear uncertainty and validation messages make it easier to correct the record before it becomes part of a policy, endorsement or other workflow. STATUS Planned next. Human review will remain central, and the available fields will vary by document type and configuration. ### Claim intimation through Customer Portal URL: https://sibro.app/claim-intimation-through-customer-portal/ Last updated: 2026-09-10T17:54:06.000Z A customer often contacts the broker first when a claim occurs. Collecting the right initial information early can make the servicing process calmer and more organised. WHAT WE ARE PLANNING Allow an authorised customer to initiate a claim through the Customer Portal, attach basic information and documents, and create a structured request for the broker’s team to review. WHY IT COULD HELP The customer gets a clear starting point, while the servicing team receives the request in the context of the correct policy. This can reduce scattered email or WhatsApp messages and improve follow-up from the first interaction. STATUS Planned next. The broker’s team will remain in control of validation, insurer or TPA communication and the subsequent claim workflow. ### Automated instalment payout calculations URL: https://sibro.app/automated-instalment-payout-calculations/ Last updated: 2026-09-10T17:53:56.000Z Instalment-based policies create repeated payout calculations across the policy period. Managing those calculations manually makes reconciliation harder as volumes grow. WHAT WE ARE PLANNING Extend payout automation to instalment-based business, with clearer visibility of the amount calculated for each instalment, what has been paid and what remains pending. WHY IT COULD HELP Operations and accounts teams could follow the financial position of an instalment without rebuilding the calculation in a spreadsheet. A consistent rule trail would also make exceptions easier to investigate and explain. STATUS Planned next. Calculation behaviour will depend on the policy schedule and the pay-in and payout rules configured by the broking firm. ### Employee e-cards in EB welcome emails URL: https://sibro.app/employee-e-cards-in-eb-welcome-emails/ Last updated: 2026-09-10T17:53:47.000Z A welcome email is most useful when it helps a covered employee take the next step immediately. WHAT WE ARE PLANNING Include relevant employee-benefit e-cards in welcome communication when they are available and approved for distribution. The message would give the member a clearer starting point for accessing healthcare benefits. WHY IT COULD HELP Employees would spend less time asking HR or the servicing team to resend a card. HR teams would have a more complete onboarding communication, and brokers could reduce repetitive service requests after a group policy goes live. STATUS Planned next. Delivery depends on the availability and quality of member, policy and e-card information. ### Secure time-limited policy document access URL: https://sibro.app/secure-time-limited-policy-document-access/ Last updated: 2026-09-10T17:53:37.000Z Policy documents often need to be shared with a customer, colleague or authorised partner. Permanent public links are convenient, but they are not an appropriate default for sensitive records. WHAT WE ARE EXPLORING Secure links that expire after a defined period and can be governed by the organisation. The design may include access duration, revocation, download controls and a record of when a link was created. WHY IT COULD HELP Teams could share a document quickly without turning it into a permanently accessible file. Time limits and revocation provide a practical layer of control when information needs to leave the main SIBRO workspace. STATUS Under exploration. Security, usability and infrastructure requirements will determine the final approach. ### Co-broking workflows URL: https://sibro.app/co-broking-workflows/ Last updated: 2026-09-10T17:53:27.000Z Co-broking business brings an additional set of questions: who owns the relationship, who services the policy, how are documents shared, and how should receivables and payouts be recorded? WHAT WE ARE EXPLORING A connected workflow for business involving more than one broker. It may cover participant roles, responsibilities, shared references, policy records and the financial treatment attached to each party. WHY IT COULD HELP Keeping co-broking arrangements inside the policy workflow can reduce parallel spreadsheets and make ownership clearer to operations and accounts teams. It can also create a better trail when the arrangement is reviewed later. STATUS Under exploration. The scope will be shaped by operational, contractual and regulatory requirements. ### Configurable views and access controls URL: https://sibro.app/configurable-views-and-access-controls/ Last updated: 2026-09-10T17:53:17.000Z Different people need different views of the same broking operation. A branch head, claims executive and accounts user should not have to work through identical screens or see identical data. WHAT WE ARE EXPLORING More configurable lists, saved views and role-based access controls across SIBRO. Organisations could tailor visible fields, filters and data scope for a role while retaining a consistent audit trail and central governance. WHY IT COULD HELP Focused views reduce screen clutter and help each user concentrate on the cases they own. Better access controls also make it easier to support branches, teams and specialist roles without maintaining separate systems. STATUS Under exploration. The final design will balance flexibility with security, supportability and consistent reporting. ### WhatsApp-assisted employee-benefits servicing URL: https://sibro.app/whatsapp-assisted-employee-benefits-servicing/ Last updated: 2026-09-10T17:52:47.000Z Many employee-benefit questions begin on WhatsApp: “Where is my health card?”, “How do I start a claim?” or “Who should I contact?” WHAT WE ARE EXPLORING A governed WhatsApp-assisted experience for common employee-benefit service needs. The aim is to help covered employees find approved information, start a request and reach the right servicing team without exposing information that should remain private. WHY IT COULD HELP A familiar channel can reduce friction for employees and repetitive queries for HR and servicing teams. The important part is not simply adding a bot; it is connecting the conversation to the correct member, policy and service workflow with appropriate consent, access and audit controls. STATUS Under exploration. Scope, safeguards and rollout order may change as we validate the experience with broking firms and their customers.