Human + SynTwin model
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
SynTwin is not a replacement channel. It is part of the same relationship between the owner and the other person.
The SynTwin scales repeatable communication. The owner keeps judgment, trust, and responsibility.
The SynTwin’s role
Section titled “The SynTwin’s role”The SynTwin is useful when the conversation depends on reusable knowledge and style.
Examples:
- Answer product questions
- Explain positioning
- Qualify interest
- Capture name, company, email, and intent
- Continue follow-up questions between meetings
- Remember prior context for a known person
- Escalate missing knowledge through reflection questions
The owner’s role
Section titled “The owner’s role”The owner stays responsible for moments that require human judgment.
Examples:
- Pricing exceptions
- Contract negotiation
- Legal or security commitments
- Sensitive relationship context
- Strategic account judgment
- Meeting the person live
- Deciding what the SynTwin should know next
How context flows
Section titled “How context flows”Context moves in both directions.
Owner teaches SynTwin.SynTwin talks to visitor.Visitor creates relationship context.Owner reviews and acts.Owner updates SynTwin.SynTwin continues with memory.This loop is what makes SynTwin different from a one-off chatbot. The SynTwin does not start cold every time. It carries product knowledge, owner style, and person-specific memory into future conversations.
Global and person-specific memory
Section titled “Global and person-specific memory”Global memory applies broadly across conversations.
Examples:
- Product facts
- Sales process
- Case studies
- Integration answers
- Security answers
Person-specific memory belongs to one relationship.
Examples:
- The visitor’s company and role
- Their concerns
- Prior questions
- Meeting outcomes
- Follow-up promises
Use global sources for facts that many visitors can hear. Use person-specific sources for context that belongs to one person or account.
Deployment boundaries
Section titled “Deployment boundaries”A deployment tells the SynTwin what it is doing in a specific context.
For example, a sales deployment might answer product questions, qualify interest, ask for email, and show a booking CTA.
The same SynTwin can have another deployment for a different purpose. The owner stays the same; the deployment goal changes the situation.
Escalation
Section titled “Escalation”A good SynTwin knows when to stop.
Escalate to the owner when:
- The answer is missing from sources
- The visitor asks for a commitment
- The topic is sensitive
- The relationship needs human trust
- The next action belongs to the owner
Use Human + SynTwin workflow to operate this model in sales conversations.