All teams

Teams / Customer care

Answer the question.
Keep the source close.

A worked example: a customer cannot accept an expired team invitation. Prepare an accurate reply and a useful internal note without changing the customer’s account.

Example workflow. Connections and live agent execution are planned.

Before assigning the task

Give the team these inputs.

The customer’s message

“My team invite says expired. Do I need to create another account?” Include the original thread and relevant invite status.

Approved guidance

The current invitation guide, resend permissions, and the escalation contact for account access.

The permitted scope

Read the request and draft an answer. No account changes, invite sends, or customer messages without review.

A brief you can adapt

One task. A defined result.

Task: Draft a reply about an expired team invitation.
Use: Current invitation guide + original ticket.
Deliver: Customer reply draft + internal case note.
If unclear: Ask for the missing detail; do not guess.

Owners and handoffs

Separate doing from reviewing.

Queue coordinator

Classify this as invitation access, capture missing details, and name the case owner.

Reply drafter

Find the approved recovery steps and write a concise answer with source references.

Support reviewer · You

Check the account-specific instructions and decide whether to send or escalate.

The working sequence

How the task moves forward.

  1. Check what the customer is actually blocked on.

    Separate an expired invitation from a failed login or missing account. Record only the details needed to identify the recovery path; never ask for a password or token.

  2. Prepare the answer from current guidance.

    Explain who can resend the invitation and what the customer should do next, only where the guide supports it. Put source links in the internal note for the reviewer.

  3. Review before sending.

    The reviewer checks permissions, the recipient, and the proposed steps. Escalate conflicting account state or undocumented behavior with a summary of what is known and missing.

The handoff

Ask for these artifacts.

  • reply-draft.md — A direct answer, the next step, and one clarifying question only if needed.
  • case-note.md — Classification, relevant guide links, known details, and any uncertainty.
  • docs-gap.md · If needed — The missing or contradictory guidance and the question it failed to answer.

Example acceptance criteria

Check the result against the brief.

  • The reply answers whether a new account is needed using an approved source.
  • Resend steps name the correct role and match the current invitation guide.
  • No unsupported expiry period, promise, or account-specific claim is invented.
  • The draft contains no credential request and remains unsent until review.

The human decision

Review the work before acting.

A support owner approves the exact message before it is sent. Access changes, refund decisions, and requests involving sensitive records move to the responsible human instead of being folded into a routine reply.

Put it in your plan

Use this as your first milestone.

Plan a queue coordinator and a reply drafter first. Add your approved knowledge sources and the point where an account-access question must escalate.