Human + SynTwin workflow

Use this page when the owner and SynTwin are not sharing context cleanly.

SynTwin uses the wrong person memory

Check whether the visitor used a generic deployment link instead of a personalized or follow-up link.

Then:

• Open the person record that should contain the relationship
• Add a note with the correct context
• Remove or correct misleading person-specific knowledge
• Share a follow-up link for the next session

If duplicate people exist, use the person record that has the most complete session history.

Visitor was not linked to the right person

This usually happens when the visitor starts from a public deployment link without identifying information.

Fix it by:

• Updating the right person record with the useful session context
• Sending a follow-up link for future sessions
• Asking the SynTwin to capture name, company, or email earlier in the deployment instructions
• Enabling email capture if the deployment should identify interested visitors

Owner cannot pick up context before a meeting

Check:

• Recent sessions for the person
• Session goal result
• Questions asked by the visitor
• Follow-up promises
• Open reflection questions
• Session-end notifications

If the context is missing, add a person note or import the meeting, email, or transcript summary through external tools.

SynTwin missed a follow-up promise

Add the promise to the person record:

Promised to send security review material after the first call. Visitor cares about SOC 2, SSO, and data retention.

Then update deployment instructions if the SynTwin should handle this pattern in future sessions.

CTA or email capture did not appear

Check:

• The deployment has the capability enabled
• The visitor matched the instruction for showing the CTA
• The email capture instruction is not too late or too narrow
• The CTA is still relevant for this deployment goal

Test the deployment with a short session after changing the instructions.

Notifications are missing or too noisy

If notifications are missing, check that notifications are enabled for the deployment.

If notifications are too noisy, tighten the send condition. Example:

Send only when the visitor asks about pricing, integration, security, or wants a follow-up.

Leave the condition broader when every session should reach the owner.

Reflection question is wrong or noisy

Dismiss the reflection question if it is not useful.

If similar reflection questions keep appearing:

• Add the missing source
• Add a person note
• Answer the question through the 1:1 screen
• Tighten deployment instructions
• Check whether the source should be internal-only instead of visitor-visible

SynTwin answered something the owner should handle

Move that topic into owner-controlled context.

Then:

• Mark sensitive sources as internal or unavailable for the deployment
• Add instructions that tell the SynTwin to escalate that topic
• Test the deployment with the same question

Use this for pricing exceptions, legal commitments, procurement negotiation, sensitive relationship context, and anything that requires human judgment.