Capture leads from document request conversations
Keep promising document requests from slipping away by capturing lead details from the relevant Docsbot conversation.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Capture Conversation Lead
Saves lead information in conversation metadata, whether or not the conversation exists.
Why this helps
A request for a generated document can contain useful lead details that are easy to lose during a busy day.
- Save lead information alongside the related conversation metadata.
- Reduce manual copying of contact details from support conversations.
- Make document requests easier to find for follow up.
Setup
Build it in a few focused steps.
- 1Connect ActiveMerge and Docsbot once in the Notis portal.
- 2Create an automation from Automations, New Automation, or tell Notis in plain language from any channel.
- 3Describe that when a document request is identified, lead information in the related conversation should be captured and saved.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real request and verify that the lead information is captured.
Questions about this workflow
Does the conversation need to exist first?
No. Docsbot says lead capture works whether or not the conversation has been created yet, as long as the available information identifies the lead.
What information can be captured?
The provided action updates conversation metadata and saves lead information. The specific fields depend on the details available in the request and the Docsbot action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to Docsbot ai. A trigger fires from one place; an action lands in another.
ActiveMerge triggers
Docsbot ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Bot
Creates a bot within a team.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Capture Conversation Lead
Saves lead information in conversation metadata, whether or not the conversation exists.
Delete Bot
Permanently deletes a bot; this action cannot be undone.
Generate Conversation Ticket
Turns a Chat Agent conversation into a structured support ticket.
Create Bot Source
Creates a source for a bot’s knowledge base.
Get Bot Details
Retrieves details about a bot in a team.
Create Webhook
Creates a bot webhook subscription; its target must be publicly accessible and support HTTPS.
Get Team Details
Retrieves details about a team, including its members and settings.
Connect any two apps with Notis in the middle.
ActiveMerge and Docsbot ai, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Docsbot ai.