> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/sac-360/sac-360-common-questions/sac-360-whatsapp/sac-360o-account-not-found.md).

# SAC 360º - Account not found

In cases of **account blocking** or **change of the WhatsApp number**, it may be necessary to replace the connected account in SprintHub.

After this change, when trying to continue an existing conversation in the **SAC 360º**, the message may be displayed:

> **"Account not found"**

This happens because the old service remains linked to the previous WhatsApp account, which is no longer connected to the system.

> **Important:** Existing services are not automatically migrated to the new WhatsApp account.

***

### How to resolve

To continue the service with the Lead, it will be necessary to start a **new conversation using the new connected WhatsApp account**.

You can do this in two ways:

* By the **SAC 360º**;
* By the Lead's **Lead**.

### Step by step

1. In the service that displays the message **"Account not found"**, click on **New Service**.
2. Select the **new WhatsApp account** that was connected to SprintHub.

   > **Note:** After connecting a new account, it may take a few minutes to become available in the selection list.
3. Confirm the creation of the service.

The system will automatically open a **new conversation** with the Lead, linked to the new WhatsApp account.

From that moment on, it will be possible to send messages normally, including text, media, quick replies, templates, and other available features.

### Demonstration video

See below the complete step-by-step guide to create a new service using the new WhatsApp account.

{% embed url="<https://www.youtube.com/watch?v=UFUa8n1GJjs>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/general/sac-360/sac-360-common-questions/sac-360-whatsapp/sac-360o-account-not-found.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.