> For the complete documentation index, see [llms.txt](https://getverifycode.gitbook.io/getverifycode-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://getverifycode.gitbook.io/getverifycode-docs/readme.md).

# GetVerifyCode Guides

Practical notes on SMS one-time codes, delivery failures, and how temporary numbers fit into verification.

These pages are written for engineers, QA, and product teams who ship phone checks. They stay vendor-neutral where it matters, and link to [GetVerifyCode](https://getverifycode.com/) when a temporary inbound number is useful.

## Start here

| Guide                                                                                   | Who it helps                                                              |
| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [How SMS Verification Works](/getverifycode-docs/how-sms-verification-works.md)         | Anyone who needs the end-to-end path from number entry to code validation |
| [When the OTP SMS Does Not Arrive](/getverifycode-docs/when-otp-sms-does-not-arrive.md) | Support, QA, and builders debugging missed codes                          |
| [Testing SMS OTP Before Launch](/getverifycode-docs/testing-sms-otp-before-launch.md)   | Teams that need a release checklist with real inbound SMS                 |

## Related

* Product: [getverifycode.com](https://getverifycode.com/)
* Interactive checklist: [getverifycode.github.io](https://getverifycode.github.io/)
* Source checklist repo: [otp-sms-testing-checklist](https://github.com/GetVerifyCode/otp-sms-testing-checklist)
* Blog: [Didn't get the verification code?](https://getverifycode.com/blog/didnt-receive-verification-code-sms-fixes)

## Editorial

Guides are maintained by Alex Carter, Editor at GetVerifyCode. Copy follows the same rules as the live site: clear, calm, no fake guarantees, and no claims about inventory we do not have.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://getverifycode.gitbook.io/getverifycode-docs/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.