> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/starter-kit/faqs/porting-and-activation-faqs.md).

# Porting & Activation FAQs

Common port-in blockers and how Reach handles them.

{% hint style="info" %}
Details available under NDA. [Request one now](mailto:hi@reachplatform.com).
{% endhint %}

<details>

<summary><strong>How do we handle device unlock requirements before porting?</strong></summary>

Porting is one of those moments that can make or break the customer experience — so we've built it to be hard to get wrong. The process is step-by-step and clearly laid out for customers on the website. Agents are trained to handle porting scenarios confidently, and we offer an AI activation and port-in bot as an add-on for teams that want to take the human load off entirely.

The most common reasons a port fails are a carrier-locked device or an incorrect account PIN. Our flows call both out explicitly — customers are prompted to verify their device is unlocked and confirm their PIN before they get anywhere near a failed transfer.

</details>


---

# 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://docs.reachplatform.com/starter-kit/faqs/porting-and-activation-faqs.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.