Collect a contact when there is a useful next step.
A visitor may need a quote, an explanation that is missing from the website, or attention from someone on the team. Sairo can collect contact information during that conversation and save a lead associated with the site and conversation.
Choose the assist or capture goal in the site settings when you want the assistant to collect leads. The answer-only goal does not expose the lead-capture tool. Test the selected goal with an enquiry before publishing the workflow.
Make the invitation specific: explain why sharing an email address or phone number will help the team follow up. Avoid making a visitor submit information merely to read an answer that is already available publicly.
Example conversation goal
A visitor asks whether a service is available for an unusual project. The assistant can explain the published scope, acknowledge the detail it cannot confirm, and ask for contact information so the team can review the request.
Review context before deciding the lead’s stage.
Open the lead together with its conversation. Check whether the request fits the business, whether the contact details are usable, and whether the assistant set an expectation that needs clarification.
Lead records support stages, an assigned person, notes, and a follow-up date. These are coordination tools for your team. A captured lead does not establish that someone is qualified, has consented to marketing, or has purchased a service.
Ask Sairo can find a lead and prepare permitted changes to its stage, notes, follow-up date or assignee. Review the proposed record before applying it. The assistant does not send a message to that lead on your behalf.
Appointment requests show their requested time and status on the lead. Check your calendar and agree the time with the visitor, then mark the request confirmed or cancelled in Sairo. Opening hours, timezone and appointment length are configured per website; this does not synchronise an external calendar.
Turn an enquiry into a follow-up. Give a captured lead an owner and a clear next action.
Before you start: A visitor has shared contact details and a lead has been captured. The workspace, visitors and figures shown are fictional examples.
Read the transcript
- An enquiry. A clear next step.
A visitor has shared contact details. Here's how to turn that enquiry into a follow-up your team can act on.
- Find the enquiry
Open Conversation inbox. Search for the visitor or the subject of their enquiry, then apply the filters. Here, we're finding Jamie Parker.
- Read before acting
Open the matching conversation. Read what Jamie asked for and the contact details they shared before deciding what should happen next.
- Open the lead
Select Jamie under Captured leads. The lead keeps contact details, ownership, progress, and follow-up notes together.
- Give it an owner
Choose the teammate responsible for the next action. After contacting the visitor, update the lead stage to Contacted so the team knows where it stands.
- Set the next action
Set the next follow-up date and add a short internal note. In this example, Dave needs to confirm an inspection time with Jamie. Select Save lead.
- Find what's due
Return to Leads and follow-ups. Select Follow-up due and apply the filters. Jamie now appears with an owner, stage, and follow-up date.
- Every lead has a next action.
Check this list each day. Follow-up dates organise your work list; they do not send automatic reminders or messages to the visitor.
Read the request
Identify the visitor’s question and the information still needed to respond.
Assign responsibility
Give an eligible teammate ownership and choose an appropriate stage.
Set a next action
Record when a reply is due and the context needed by the person handling it.
Update after follow-up
Record the actual result after the team has contacted the visitor.
Keep client information in the correct workspace.
Agency memberships can be restricted to a client project. Access to leads and related conversations follows that scope, and internal notes remain distinct from client-facing information.
Test a rollout using contact details your team controls. Confirm that the lead appears under the intended site and that the person responsible can access it. Check the same path again when a site changes project or its team changes.
Measure the complete journey.
Sairo reports conversations that produced lead records, which helps you see whether visitors are choosing to share details. Review lead quality separately: an automated capture count is not a sales result.
Compare periods using the same site and date range. Look at a sample of both captured and uncaptured conversations before changing the greeting or asking for more information. A lower capture rate may be appropriate when more visitors find the answer immediately.
Common questions
Does Sairo send leads to a CRM automatically?
The current built-in workflow stores and manages leads in the Sairo workspace. This page does not describe a native CRM synchronisation. Confirm any external workflow separately before relying on it.
Does a captured lead confirm an appointment?
No. Your team must confirm availability and any booking through its actual scheduling process.