Skip to content

Sales owner playbook

Use this playbook when you want SynTwin to take over parts of a sales conversation without losing human context.

1. Prepare the deployment

Section titled “1. Prepare the deployment”

Open the sales deployment and check:

  • Goal says what the SynTwin should achieve
  • Instructions say when to qualify, ask for email, show a CTA, and escalate
  • Product, pricing, security, and customer story sources are attached
  • Email capture is enabled if visitors should identify themselves
  • Notifications are enabled if you want session recaps

2. Send outreach

Section titled “2. Send outreach”

Send a short email with a SynTwin link.

Example:

Hi Alice,


If useful, you can ask my SynTwin a few questions before we talk:
https://...


It can answer product questions and help us make the first call more specific.

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

3. Let the SynTwin handle first interest

Section titled “3. Let the SynTwin handle first interest”

The visitor can ask questions, explain their situation, and leave an email.

The SynTwin should:

  • Answer from approved sources
  • Ask short qualifying questions
  • Capture name, company, and email
  • Show the next-step CTA when useful
  • Create or update the person record

4. Prepare for the meeting

Section titled “4. Prepare for the meeting”

Before the meeting, open the person record and recent sessions.

Check:

  • What the visitor asked
  • What the SynTwin answered
  • Whether the goal was reached
  • Fit signals
  • Concerns or objections
  • Follow-up promises
  • Open reflection questions

Start the meeting from that context:

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

5. Update the SynTwin after the meeting

Section titled “5. Update the SynTwin after the meeting”

After the call, add a person note.

Example:

Alice from Acme is interested, but security review is the next blocker. She cares about SOC 2, SSO, data retention, and references from similar companies.

If you have meeting notes, transcript summaries, or email summaries, attach them as person-specific context.

6. Continue follow-up

Section titled “6. Continue follow-up”

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

Example:

You can keep asking my SynTwin here if anything comes up before our next call:
https://...

Use the SynTwin for repeatable answers. Step in yourself for pricing exceptions, negotiation, legal commitments, trust moments, or anything missing from sources.

7. Resolve unresolved questions

Section titled “7. Resolve unresolved questions”

During daily review:

  • Read important sessions
  • Answer reflection questions
  • Add missing sources
  • Update the person record
  • Tighten deployment instructions
  • Mark handled sessions read

Done state

Section titled “Done state”

The loop is working when:

  • The visitor has a person record and contact path
  • The SynTwin can answer common questions between human meetings
  • The owner can join a meeting with context
  • Meeting outcomes become memory
  • Open questions become owner actions or source updates

Related guides: