Daily owner workflow

After setup, use SynTwin as a daily communication loop.

10-minute triage

When you are busy, do only this:

1. Open Monitor > Sessions.
2. Review unread sessions from high-value deployments.
3. Look for email captured, next-step request, pricing/security/integration question, or follow-up promise.
4. Open Train > Reflections only for questions tied to active deals.
5. Add one person note for any meeting or follow-up you handled outside SynTwin.

Skip everything else until later.

Handled means one of these is true:

• You replied yourself
• The SynTwin can answer next time
• The person record has the context
• The deployment instructions were fixed
• The item is irrelevant and dismissed

Morning review

Start with the conversations the SynTwin handled while you were away.

1. Check unread sessions

Open Monitor > Sessions.

The sidebar shows an unread badge when new sessions need review.

Scan unread sessions for:

• Goal reached
• Good leads
• Confusing answers
• Missing facts
• Follow-up promises
• Owner-only topics

Mark sessions read when handled. Use Mark all read after reviewing a batch.

2. Review reflections

Open Train > Reflections.

Answer open questions that represent real knowledge gaps.

Dismiss questions that are irrelevant or already handled.

For important questions, start a 1:1 chat or call from the question card.

3. Check notifications

Review session-end notifications for high-value deployments.

If notifications are noisy, tighten the send condition.

If notifications are missing, check the deployment notification settings.

Before meetings

Use the SynTwin’s context to make human conversations warmer.

Open the person record for each upcoming meeting.

Check:

• Latest visitor summary
• Questions asked before the meeting
• Product, pricing, security, or integration concerns
• Follow-up promises
• Missing facts or open reflection questions

Add any context the SynTwin should know before the visitor returns.

Copy the important bits into your meeting notes:

Asked before meeting:
- Rollout risk
- Salesforce integration
- Security review

SynTwin promised:
- Owner will follow up with implementation references

After meetings

Teach the SynTwin what changed outside SynTwin.

4. Update people

Open Monitor > People.

For active leads or customers, keep summaries and person sources current.

Add notes after calls, emails, or meetings that happened outside SynTwin.

Example:

Alice from Acme wants security review next. Her main blocker is procurement risk, not product fit.

If you have notes, transcripts, or email summaries from external tools, attach them as person-specific context.

End-of-day cleanup

Close the loop before the next day starts.

5. Tune deployments

Open the deployment dashboard.

If the goal success rate drops or sessions feel off:

• Tighten the goal.
• Add or remove sources.
• Adjust instructions.
• Add a CTA or email capture.
• Change channel availability.

6. Teach through 1:1

Use the 1:1 screen when the update is easier to explain conversationally.

Examples:

Alice from Acme now cares most about procurement risk. Remember that for future conversations.

Our inbound demo deployment is asking too many questions before explaining the product. Make it more direct.

7. Prepare follow-up

For active conversations:

• Send follow-up links when visitors should continue through the SynTwin
• Answer unresolved questions the SynTwin escalated
• Check notifications for high-value deployments
• Update the CTA if the next step changed

Where to look

• Sessions — what visitors said and what the SynTwin answered
• Reflections — questions or improvements the SynTwin raised for you
• People — relationship memory for leads and customers
• Notifications — session recaps outside the app

See Human + SynTwin workflow for the full sales loop.