Skip to main content
A user has one Text account, which can belong to several organizations. Within each organization, an agent record stores that user’s chat settings and group memberships.
Text uses different terms for people and teams in the app and APIs. The Text app calls people who handle conversations teammates. The API represents those users as agents. The app uses team as a general term, while the APIs use groups to route chats and teams to route tickets.

Organizations

An organization brings together the accounts, chats, tickets, and settings for one business or workspace. A few things to know:
  • Every organization has at least one account and one owner.
  • One account can belong to multiple organizations.
  • Each account has a default organization that opens when the account signs in.
Most APIs identify an organization with organization_id. Some APIs and client-side configuration use license_id. There is no general public endpoint for converting between them, so retrieve and store the identifier required by each API.
Find organization_id in the Text app or retrieve it with List organizations. For an API that requires license_id, use Get license info.

Accounts and agents

A user who signs up to Text has one account with an account_id. Organization membership connects that account to an organization. The Configuration API represents this user within that organization. If one account belongs to several organizations, its agent settings can differ in each organization. One Text account can belong to more than one organization One Text account can belong to more than one organization

Chatting groups and ticketing teams

The APIs use separate resources for routing chats and tickets: