Support
Get help with your Phonekit workflow
Tell us what you’re trying to connect and where the workflow stops. Start with the guides below, or send an access or support request so we can follow up about your setup.
Start with the guide for your connection
The quickstart covers the path from workspace access to using a number. The CLI guide explains local connection and message retrieval. The API reference covers selected-number reads and explicitly authorized management operations. Reads return immediately; SDK and CLI wait helpers poll locally.
If you’re adding Phonekit to a test runner, use the Playwright or CI guide. Assistant installation pages explain the CLI, skill or hosted MCP connection appropriate to each environment, including what has been tested.
- Quickstart
- CLI setup and commands
- API reference
- Playwright SMS testing
- CI configuration
- Assistant installation guides
For a delivery issue, describe the step that failed
Include the service or application, the verification step, the approximate time and time zone, and whether the service accepted the number. Note whether you saw a send confirmation, a number rejection, or a timeout waiting for the message.
For an automated workflow, include the CLI version or API endpoint and a sanitized error. Tell us whether the wait started after a cursor captured before the send request. That helps distinguish message selection from delivery and account-state problems.
Share enough context to investigate
Do not include API keys, cookies, passwords, recovery codes, or full verification messages in your request. A number label, general workflow description, timestamp, and sanitized error are a useful starting point.
If the problem concerns an outside account, keep its private account details out of the initial request. We can establish what information is needed after understanding the issue. Your company’s account administrator may also need to review that service’s own settings.
Tell us about the workflow you need
Use the request form for setup questions, number requirements, and integration needs. Include a work email we can reply to and a short description of the workflow. Choose team access, programmatic access, or both.
For number availability, include the country and whether mobile classification or an existing number is required. For an agent connection, name the assistant and where it runs. We’ll use that context to confirm the available path.
Questions you may have
What should I check after a receiving timeout?
Confirm the destination and that the position was captured before send. Check the application’s accepted send and provider status if available. Report the stage and approximate time before trying another request.
What does unauthorized or unavailable number mean?
Check the runtime’s credential and selected-number scope. A number outside that key’s grant is unavailable even if you can see it through another authorized route. Use the API errors or CLI exit codes for your interface.
Can you confirm a service accepts a number?
Share the exact service, country and verification step. We can discuss an available option and the appropriate check. Actual service acceptance needs evidence from that flow rather than an assumption based only on SMS capability.