Skip to main content
Phone numbers are the public entry points for live calling and SMS. They decide where inbound traffic lands and which identity outbound traffic uses.

Number Roles

  • Inbound voice numbers receive live calls into an agent or squad
  • Outbound voice numbers are used when Feather places calls
  • SMS-linked numbers are attached to text-capable agents for thread creation
  • Bridging numbers are available for advanced call routing and transfer flows

Common Setup Patterns

Inbound Support Line

Assign one number to an agent or squad so callers land in a stable entry point.

Outbound Campaign Pool

Provision one or more outbound numbers and let calls or workflows use them for caller identity.

Dedicated SMS Number

Link a number to a text agent so the thread experience stays consistent for the recipient.

Typical Setup Order

  1. Connect or import a Twilio-backed number into Feather
  2. Decide whether the number is for inbound, outbound, SMS, or a squad entry point
  3. Test direct dispatch or a thread creation flow
  4. Add workflows, routing, or transfers once the base path works

List Existing Numbers

curl "https://prod.featherhq.com/api/v1/phone-numbers" \
  -H "X-API-Key: $FEATHER_API_KEY"

Things to Plan For

  • Which number should represent each brand or team
  • Whether inbound calls should land on one agent or a squad
  • Whether SMS should use the same number as voice or a dedicated thread identity
  • Which outbound numbers should be available to workflows
  • Use Dispatch for one-off outbound calls
  • Use SMS Threads for text conversations
  • Use Squads when one number should route across multiple specialists