Human + SynTwin workflow

SynTwin works best when the owner and SynTwin share context.

This is an advanced workflow guide. If you want the fastest sales path, start with First sales loop or Sales owner playbook.

The SynTwin handles repeatable conversation. The owner steps in for judgment, trust, negotiation, and relationship moments.

Prerequisites

Before using this workflow, make sure you have:

A deployment with the right interaction modes enabled
Deployment instructions that tell the SynTwin when to qualify, capture email, show a CTA, or escalate
Relevant product and company sources attached to the SynTwin
Person-specific context for known visitors
A deployment link, personalized link, or follow-up link ready to share
Notifications enabled if the owner should receive session recaps

Use these guides if a prerequisite is missing:

Owner handoff checklist

Before outreach

Choose the deployment for this sales motion
Check that the deployment has the right sources selected
Check that email capture or the next-step CTA is enabled
Use a personalized link if you already know the visitor
Send the SynTwin link in the outreach message

Before the meeting

Open the person record
Review recent sessions
Check the visitor summary, fit signals, goal result, and questions asked
Check follow-up promises and open reflection questions
Add missing context before the meeting if the SynTwin discovered something important

After the meeting

Add a person note with what changed
Add meeting notes, email summaries, or transcript context if available
Answer or dismiss reflection questions
Update deployment instructions if the same gap will recur
Send a follow-up link if the visitor should keep asking questions through the SynTwin

Before follow-up

Confirm the visitor is linked to the right person
Confirm unresolved questions have an answer or owner action
Check that the next-step CTA still matches the relationship
Review notification settings if the owner needs to see future sessions

Example workflow

1. Send outreach

The owner sends an outreach email with a SynTwin link:

If useful, you can ask my SynTwin a few questions here before we talk.

Use a personalized deployment link when you already know the visitor’s name, company, email, or context.

Done when the visitor has a link that routes to the right deployment and person context.

2. SynTwin handles first interest

The visitor talks to the SynTwin.

The SynTwin can:

Answer product questions
Qualify interest
Ask for name, company, and email
Show an email capture form
Show a booking or next-step CTA

The session creates or updates a person record.

Done when the visitor’s interest, questions, and contact details are captured.

3. Owner gets context

The owner reviews the session or receives a session-end notification.

Before scheduling or joining a meeting, the owner checks:

Visitor summary
Goal result
Questions asked
Fit signals
Follow-up promises
Any open reflection questions

Use Review and improve sessions when you need to inspect what happened. Use Daily owner workflow when this becomes a recurring operating rhythm.

Done when the owner knows what the visitor cares about and what the SynTwin already said.

4. Visitor returns before the meeting

The visitor may come back with another question.

Use a follow-up link so the next session attaches to the same person.

The SynTwin resumes with memory instead of restarting discovery.

Done when the new session updates the same relationship instead of creating isolated context.

5. Owner takes the meeting

The owner can pick up where the SynTwin left off:

I saw you asked about rollout risk and Salesforce integration. Let's start there.

This makes the human meeting warmer and more specific.

Done when the owner uses the SynTwin’s context to continue the conversation naturally.

6. Owner updates the SynTwin

After the meeting, the owner adds what changed.

Use the 1:1 screen or add a person note:

Alice from Acme wants security review next. She cares most about procurement risk and needs references from similar companies.

This becomes person-specific context for future conversations.

Use Manage people for person notes. Use Connect external tools when meeting notes, email summaries, or transcripts should be imported from another system.

Done when the SynTwin knows the meeting outcome and next relevant context.

7. SynTwin handles follow-up

The visitor asks follow-up questions.

The SynTwin answers from available sources and person memory.

If something is missing, SynTwin can raise a reflection question for the owner.

Done when answerable follow-up questions are handled without losing relationship context.

8. Owner resolves gaps

The owner answers unresolved questions by:

Responding in 1:1
Adding a source
Updating the person
Editing deployment instructions
Importing meeting notes or email summaries through external tools

The next visitor conversation benefits from that update.

Done when the gap is resolved for this visitor and, when useful, for future visitors too.

When the owner should step in

The owner should take over when the visitor needs:

Pricing, negotiation, procurement, or contract judgment
Legal, security, or compliance commitments
A sensitive relationship moment
A human meeting, introduction, or internal escalation
An answer that is not covered by the SynTwin’s sources
A decision that depends on private context the SynTwin should not know

Operating principle

Do not treat the SynTwin as a separate channel.

Treat it as part of the same relationship:

SynTwin warms and remembers.
Owner handles high-trust moments.
SynTwin follows up and escalates gaps.
Owner teaches SynTwin.

Done state

The workflow is healthy when:

The visitor has a person record and contact path
The owner can review what happened before meeting or replying
Meeting outcomes become person-specific context
Unresolved questions are answered, assigned, or dismissed
Follow-up sessions attach to the same person
Deployment instructions improve when the same gap appears repeatedly