How do you connect AMS360 to your inbox so that a client email lands in the right client file?
You put Bombos next to your inbox and AMS360: it reads the client's email and the attachment, finds the client and the policy in AMS360 and proposes the place in the file, with the confirmation drafted. Someone on your team reviews it and presses Approve in Bombos. Only then is the document filed and the confirmation sent. Bombos works next to AMS360, not instead of it.
What Does AMS360 Already Do, and What Not?
AMS360, by Vertafore, already does a lot by itself. Carriers download new policies, endorsements, claims and renewals directly into it, so nobody types them in. Vertafore has built AI into AMS360 as well: the Email Agent interprets incoming emails, summarizes them and triggers the right workflows, and a Policy Intake Agent that turns commercial policy documents into structured AMS360 data is with early adopters.
Next to that, your agency has its own way of working that lives with your people. One CSR knows that a certain client always sends claims from the office manager's address. Another knows that photos sent by text message belong with last week's claim form. When a form comes in, someone still decides which file it goes in, what the confirmation says and whether anything is missing.
That is the preparation Bombos does. It reads the email and the attachment, finds the client and the policy in AMS360, and proposes the file with the reason underneath and a draft confirmation. What only one colleague knows, Bombos asks about and records, so the whole team works from the same rule and it counts the next time.
Which Tasks Run on AMS360?
Each task below starts with an email to your agency and ends, after your approval in Bombos, in the client file in AMS360 or in a reply to the client. Claim forms and change requests are a good first task, because they arrive daily and your team already knows what the right result looks like. Meeting prep and the status question come next, with the details from AMS360 and the email history brought together on one page. Everything AMS360 already does by itself keeps running as it does today; Bombos adds the preparation your people now do by hand. You start with one task. After that, your own team teaches Bombos the next one, and you do not need to be technical for that.
What Changes in Your Week?
When your agency grows, the pile of incoming forms grows with it, and the usual answer is another CSR. With Bombos, the forms arrive with a proposal and a draft, and your current team reviews them. What one colleague knows becomes something everyone can use, so a holiday no longer means a backlog. That is how the same team does more work, at a higher quality, for less than half a day a week of the employee you would otherwise hire.
It starts with one task. We set it up together with you, with your own AMS360 and your own inbox, and we go through the first proposals with you on a call. Each correction, with its reason, makes the next proposal better. After that you can do it yourself, and your team adds the next task. Do more with the same team, and keep AMS360 at the center of your agency.
What Doesn't Go Out Without Your Approval?
Bombos files nothing in AMS360 and sends no confirmation or reply to a client until someone at your agency has pressed Approve in Bombos. A confirmation says the form has arrived, not that the claim is covered. Bombos handles property and casualty claims only, not life insurance, disability coverage or health data. That limit is always on. Only Bombos can switch it off, at your explicit request and at your own risk.
For every step you can read back afterwards what happened and why. For the work inside your office, such as looking things up, checking and preparing, you decide how much Bombos does ahead of time; messages to customers and payments always wait for your approval. A proposal can be wrong, even when the reason sounds believable. When in doubt, Bombos asks instead of guessing.
Bombos also works with HawkSoft, EZLynx, and QQCatalyst.
All tasks Bombos takes on are listed under use cases.