Quote to policy
When to use it
Section titled “When to use it”- You are a digital insurer, an MGA or a broker who quotes online, and most quotes never turn into policies.
- You want an advisor to call only the people who are still thinking, not everyone.
- You want new policyholders to know how to claim from day one.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| A form people fill in | The Get a quote form this playbook creates (when you choose the form option): put its link on your website, WhatsApp and social bios. No code needed. |
| A form your staff fill in | The Policy sold form your advisors fill in when a customer buys, matched by phone. It stops the follow-up and sends the welcome. |
| Events from your app or website (needs a developer) | Or, with the app option, your app sends a quote event (with the product) and a purchase event. |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Team | Advisors | Calls customers who haven't bought two days after their quote. | Empty |
| Team | Sales managers | Gets the weekly report. | Empty |
| Form | Get a quote | The quote request form (the no-code way in). The product is saved with the request. | Draft, not published |
| Form | Policy sold | Staff-only form an advisor fills in when a customer buys. It stops the quote reminders and sends the welcome. | Draft, not published |
| Question | Report: quotes requested | How many people asked for a quote on the form (used by the weekly report). | Ready |
| Question | Report: policies sold | How many sales advisors recorded. | Ready |
| Question | Report: quotes created | How many people got a quote in the app (used by the weekly report). | Ready |
| Question | Report: policies purchased | How many people bought a policy in the app. | Ready |
| Report | Weekly: quotes and policies | Each week, quotes, purchases and the state of the advisor calls, to the managers. | Off |
| Template | Your quote is waiting (email) | Reminder email two hours after the quote. No amounts. | Ready |
| Template | Your quote is waiting (SMS) | Next-day SMS reminder. | Ready |
| Template | Welcome and how to claim (email) | Welcome email with how to claim and where the policy document is. No policy number, no amounts. | Ready |
| Template | Welcome (SMS) | Short welcome SMS. | Ready |
| Follow-up | Quote 1: follow up until they buy | A quote request gets a reminder email, an SMS and then an advisor task, each only while the customer hasn't bought. | Off |
| Follow-up | Quote 1: follow up until they buy | A quote created in the app gets a reminder email, an SMS and then an advisor task; it ends when the policy is purchased. | Off |
| Follow-up | Quote 2: policy sold | When an advisor records a sale, stop the reminders and send the welcome. | Off |
| Follow-up | Quote 2: policy purchased | When the app records a purchase, mark the customer as a policyholder and send the welcome. | Off |
The questions it asks
Section titled “The questions it asks”| # | Question | Default | Fills in |
|---|---|---|---|
| 1 | What should messages call your company? | none, must answer | org_name |
| 2 | How do quotes and sales reach Origamy? Choose form (no code: a quote form and a staff sold form) or app (your app sends events). | form | quote_source |
| 3 | Which team calls customers who haven't bought after two days? (one person is fine) | Advisors | advisor_team |
| 4 | Which number should customers call to make a claim or ask a question? | ‹workspace phone› | claims_phone |
| 5 | Where can customers finish buying their quote? (a link; leave empty to give your phone number only) | empty: skipped | finish_url |
Other settings
Section titled “Other settings”These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|---|---|
| Event your app sends when a quote is created (with a product property) | quote.created | quote_event |
| Event your app sends when a policy is bought | policy.purchased | purchased_event |
| Products on the quote form | Motor, Home, Travel, Business | products |
| Where customers find their policy document | in your account in the app and in the email we sent you | docs_where |
| Who gets the weekly report | Sales managers | manager_team |
| How long after the quote the reminder email goes | 2h | email_delay |
| Wait after the email before the SMS (a day after the quote, minus the email delay) | 22h | sms_delay |
| Wait after the SMS before the advisor task | 1d | call_delay |
| Hours the advisor has to call | 24 | call_due_hours |
| When the weekly report arrives | 0 8 * * 1 | report_cron |
| Default phone country on the forms | ‹workspace country› | default_country |
| Time zone for the report | ‹workspace timezone› | timezone |
| Sender address | ‹workspace default_sender› | email_from |
| Greeting when a first name is missing | there | greeting_fallback |
Timings
Section titled “Timings”- 2h after the quote, a reminder email.
- A day after the quote, an SMS.
- Two days after the quote, a call task for Advisors, due in 24 hours.
- Every step checks that the customer hasn't bought yet. The moment a policy is recorded as sold, the reminders stop and the welcome email and SMS go.
- The weekly report arrives on cron 0 8 * * 1 in ‹workspace timezone›.
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| The quote reminder and the welcome | A verified sending domain for ‹workspace default_sender›. | |
| sms | The next-day reminder and the short welcome | An SMS provider, or Origamy managed SMS after business verification (KYC). |
What you need to do
Section titled “What you need to do”- With the form option: publish the Get a quote form and the Policy sold form. Advisors fill in Policy sold, with the phone number from the quote, as soon as a customer buys. With the app option: send quote.created (with a product property such as motor or travel) and policy.purchased from your app.
- Add people to the Advisors and Sales managers teams. A task assigned to an empty team reaches nobody.
- Never put a premium, an amount, a policy number or a claim detail in a message, an event property you copy into a message or a task note. Messages point to the app, the email and your phone number instead.
- Check your insurance regulator's rules on how you may contact people who asked for a quote, and say on the quote form that you will follow up. Don't tell anyone they are covered until the policy is issued.
- Verify the sending domain for the email, connect an SMS provider or finish business verification, switch the follow-ups and the report on, and test with your own phone and a fake quote.
- Choose the form option if you have no developer. Put the Get a quote link on your website, WhatsApp status and social bios, and have advisors fill in Policy sold the same day a customer buys, using the phone number on the quote. If your app already has quotes and purchases, choose the app option and send two events instead.
- The call after two days is where most quotes are won. Make sure the advisor team has people in it, and ask them to note what was holding the customer back (price, cover, trust, timing) in their own words, without amounts.
- Never put a premium, a policy number or any claim detail in a message. Messages point to the app, the email and your phone number, which also keeps you on the right side of your insurance regulator’s rules on advertising and customer notices.
- Many customers pay by bank transfer, mobile money or at an agent rather than by card. If that is how yours buy, change the reminder wording to say so and put your buy link or phone number in the settings, and tell advisors to record a sale only when the payment has cleared.
This playbook is synthesized: no customer has run it with us yet. If you build it, tell us what you changed, and we’ll replace it with the real version.
Copilot eval
Section titled “Copilot eval”The request used to test the copilot on this playbook (a live eval):
We're an online insurer with a quote request form, and our advisors record sales on a form. When someone asks for a quote, email them a reminder after 2 hours and text them the next day, and if they haven't bought after 2 days give an advisor a task to call. Stop as soon as they buy. When a policy is recorded as sold, send a welcome that explains how to claim and where the policy document is. Send the manager a weekly report of quotes and sales. Never put a premium, an amount or a policy number in a message.
It passes when every piece is a valid draft and everything lands off, with at least: form, workflow, message_template, report. It must never use: premium, policy number.