Skip to content

Document the pay-as-you-go payment-method requirement on the SMS pages - #1195

Open
chiranjeet-vapi wants to merge 1 commit into
VapiAI:mainfrom
chiranjeet-vapi:docs/sms-payment-method-requirement
Open

Document the pay-as-you-go payment-method requirement on the SMS pages#1195
chiranjeet-vapi wants to merge 1 commit into
VapiAI:mainfrom
chiranjeet-vapi:docs/sms-payment-method-requirement

Conversation

@chiranjeet-vapi

Copy link
Copy Markdown

Description

  • Inbound SMS replies are generated by the Chat API and inherit its billing requirement: on a pay-as-you-go org there must be a saved payment method (and one completed payment while the org is under 30 days old), otherwise the text is received, a session is created, and no reply is sent, with nothing shown in the Dashboard.
  • That requirement is documented only in the Troubleshooting table on chat/quickstart. The two pages an SMS customer actually follows, chat/sms-chat and phone-numbers/inbound-sms, did not mention it. Two support tickets in the last two weeks were opened as "SMS is broken" for exactly this reason.
  • Adds a Prerequisites bullet and a <Warning> callout to fern/chat/sms-chat.mdx, and a Requirements bullet to fern/phone-numbers/inbound-sms.mdx, both linking to /chat/quickstart#troubleshooting and /billing/manage-billing-and-credits.

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work

🤖 Generated with Claude Code

Inbound SMS replies run through the Chat API and inherit its billing gate:
a pay-as-you-go org needs a saved payment method (and one completed payment
during its first 30 days) or the text is received, a session is created, and
no reply is ever sent, with nothing shown in the Dashboard. This was only
documented under Troubleshooting on chat/quickstart; the two pages an SMS
customer actually follows said nothing about it. Adds a Prerequisites bullet
and a Warning to chat/sms-chat and a Requirements bullet to
phone-numbers/inbound-sms, both linking to the existing troubleshooting table.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@lightsage-app

lightsage-app Bot commented Sep 5, 2026

Copy link
Copy Markdown

Lightsage docs evals

Waiting for the staging docs URL before running evals.

Lightsage will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes.

Commit: 0d64b1e
Status: waiting for staging docs URL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant