# Choosing Fast Send vs Dedicated Number

Canonical URL: https://texttree.ai/en/docs/fast-send-vs-branded-number/
Markdown URL: https://texttree.ai/en/docs/fast-send-vs-branded-number.md
Page type: docs
Translation status: approved
Legal status: not_required

## Summary

Decide whether to start with the quickest SMS path or buy a recognizable sender number.

## Source content

# Choosing Fast Send vs Dedicated Number

TextTree launch onboarding has two product paths.

## Fast Send

Choose Fast Send when you want to prove the SMS workflow quickly.

Use this path when you need to:

- create a scoped bearer token
- set a spend limit
- send the first test SMS
- inspect message status, failures, cost, and webhook events

Fast Send can use the configured sender path first. It is the right starting
point for API testing, prototypes, reminders, alerts, and early AI-agent flows.
Dashboard quick-send and the Send page still use the same suppression, spend,
idempotency, sender, and provider checks as API sends.

## Dedicated Number

Choose Dedicated Number when sender identity matters.

Use this path when you need to:

- buy or connect a phone number
- configure inbound SMS routing
- show operators which number owns the conversation
- prepare registration or compliance state before higher-volume live traffic

Dedicated Number is the better path for customer support, campaigns, high-volume
workflows, and teams that need replies tied to a recognizable sender.
After a branded number is connected, operators can select it for one-off sends
from the dashboard or Send page. If they leave sender selection automatic,
TextTree chooses the configured sender path for the workspace.

## Shared controls

Both paths still use the same safety and operations model:

- workspace and campaign suppressions gate outbound sends
- spend limits gate cost-incurring sends
- selected branded senders must remain connected to the workspace
- provider callbacks must be verified before reconciliation
- logs and webhook replay keep delivery inspectable
- API and MCP access use TextTree-issued scoped bearer tokens