Sign in

Provision the default conversation statuses for a new account

When the Platform Operator provisions a company, the system seeds the six default conversation statuses — the five system statuses plus In Progress — so the company's Inbox has a working status set before its first conversation.

When this happens: The provisioning seeder runs during UC-12.9.

How it works

  • As part of provisioning, inserts six ConversationStatus rows for the new tenant: New, In Progress, Waiting for Customer, Follow-up, Resolved, Refused/Lost, in that display order.
  • Sets SystemKey on New, Waiting for Customer, Follow-up, Resolved and Refused/Lost; leaves it unset on In Progress.
  • Sets Resolved and Refused/Lost as terminal, and Refused/Lost alone as requiring a reason.
  • Assigns the default color to each status and sets ReopenTargetStatusId to the newly seeded In Progress status.
  • Seeds the Refused/Lost reason list with its default options in the same seeding pass.
  • Continues provisioning.

Other paths

Retried provisioning

Provisioning fails and is retried (UC-12.9 ). Statuses already inserted are not duplicated — the seeder is idempotent per tenant, the same pattern the predefined-list seeder already uses.

Good to know

  • Every company starts with exactly the same six statuses, five of them system-protected.
  • The default set is seeded in the same pass as the predefined lists and pipeline stages.