Business address
SimpleX business addresses can accept customer requests while creating separate support conversations.
business messaging privacy
Offer private customer conversations without improvising the support desk.
Use the planner to turn upstream SimpleX Chat concepts into a concrete rollout, support, relay, and data-boundary decision.
Unofficial boundary
AGPL-3.0 source
v6.5.5 release noted
Workflow
What this page helps decide.
Team handoff
A business conversation can involve more than one support person, so role and escalation rules matter.
Broadcast caution
Broadcasts and customer groups need governance, consent, and moderation rules before public use.
Decision matrix
What the planner checks before a rollout.
| Area | Question | Planner output |
|---|---|---|
| Identifiers | How will users connect without phone numbers, handles, or global IDs? | Invitation, address, and group workflow map. |
| Relays | Do preset servers satisfy the pilot, or does the team need self-hosted SMP relays? | Relay posture, domain checklist, and operations tasks. |
| Data ownership | Who owns backups, device loss, passphrases, and profile recovery guidance? | Device-owned data policy and support script. |
| Business support | Does customer support need business addresses, broadcasts, or bot handoff? | Support conversation model and moderation checklist. |