> For the complete documentation index, see [llms.txt](https://docs.truecaller.com/truecaller-for-business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truecaller.com/truecaller-for-business/features/inbound-message-cta.md). # Inbound Message CTA {% hint style="info" %} The Inbound Message CTA lets users reply to your verified business call through a chat message sent to your registered sender ID. Message CTA taps on that business across the After Call Screen, and Details View redirects users into a live two-way Business Chat conversation with the configured Sender ID. {% endhint %}
What exactly is an Inbound Message CTA?
How can I enable the Inbound Message CTA capability?
What changes for the end user?
Which surfaces are covered?
What happens if a business hasn’t configured a channel?
Can a business use the same Sender ID across multiple Business Pages?
What are the prerequisites to activate it?
What validations are performed while configuring the Sender ID, and what errors can occur?
Can configuration errors block the rest of my Business Page?
How quickly do changes take effect?
What analytics will we get?
Is it secure and compliant?
--- # 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.truecaller.com/truecaller-for-business/features/inbound-message-cta.md?ask=&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.