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

# FAQ

{% hint style="info" %}
**If you have any more questions, please feel free to ask!**
{% endhint %}

<details>

<summary>Will this work with different carrier SIM cards?</summary>

This needs to be tested more, but users have reported that it does not. So it's recommended to use the same carrier or MVNOS on the same network for now.

* **EXAMPLE:** Boost = AT\&T

</details>

<details>

<summary>How long will my number stay registered?</summary>

That's a good question, will update more on this later, but this method has been super reliable for me so far **(\~2 months in)**.

</details>

<details>

<summary>Do I need to turn off my iPhone or change the phone number in my Settings at all during this process?</summary>

No! Not like the other methods, huh? I didn't have to turn off the phone or change anything in the settings at all during this process, making it so easy!

* This does not include the methods that require you to change your number in your settings. This only implies to the first Physical SIM method and eSIM methods.

</details>

<details>

<summary>Which method would be best for me?</summary>

It all depends on what carrier you're using and what your SIM preference would be. If you're already using an eSIM, I would use the eSIM methods.

</details>

<details>

<summary>Does my phone need to stay on 24/7?</summary>

I'm still testing this, but as of now, it doesn't seem necessary, but I personally think it's still recommended.&#x20;

When I first did the method, I kept mine on 24/7 because I always had no luck after turning off my iPhone, my number would always deregister from iMessage, but it never did that with this method **(\~3 months in, even with the iPhone off).**

</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://atbluebubbles.gitbook.io/guide/overview/faq.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.