Subcontext lets regulated firms have conversations with their customers, with AI agents and tools to quote, sell and follow up. As a developer, you can add these to your firm's website and connect them to your own systems.
What you can build#
- Your AI agent on your website. A chat window where visitors talk to your firm's agent, by typing or by voice. Conversations appear in your Subcontext inbox, where your team can join in.
- Quotes and sales. A quote form for one of your products, from the first question to buying the policy, on your own pages.
- Lead capture. An enquiry form for a campaign, or code that sends the leads from your own forms into Subcontext.
- Help beside your forms. An AI helper next to any form that answers questions as people fill it in.
- Tools for your advisers. The "Nurture with AI" adviser tool inside your portal or CRM.
- Your own integrations. Your servers can send leads in, read your products and report what happened to each lead, using the Subcontext API.
Most of these start with a snippet you copy from your Subcontext dashboard and paste into your page. The website embeds section covers each one, with its options and complete example pages.
What you need#
- A Subcontext account for your firm. The embeds and the API work with the agents, products and campaigns you set up in the dashboard. If your firm doesn't use Subcontext yet, email hello@subcontext.com.
- Access to your website's code, or someone who has it. Most embeds need
a snippet pasted before
</body>. - For the API: a server that can keep a secret, and an owner of your Subcontext organisation to create an API application.
Where to go next#
- Keys and tokens explains which embeds need only a public key, and when you need an access token.
- To add something to your website, start with the website embeds.
- To connect a server, start with access tokens.
- For addresses, testing and support, see environments and support.