> 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/verified-campaigns/faqs/how-will-verified-campaigns-impact-my-ceps-billing.md).

# How will Verified Campaigns impact my CEP’s billing?

Verified Campaigns operates independently of your Customer Engagement Platform (CEP) and does not alter its billing structure. 

Since our platform integrates via webhooks, your CEP will continue to charge you based on its existing pricing model—whether that’s based on **API calls, events triggered, messages sent, or MAUs** (Monthly Active Users).

Here’s what you need to consider:

✔ **No Double Charging** – Verified Campaigns does not duplicate billing for the same user engagement. If you’re already paying your CEP for event-based triggers, our pricing remains separate and purely based on the unique Truecaller users reached within a calendar month

✔ **Webhook-Based Triggers** – Since Verified Campaigns relies on webhook integrations, any event-triggered campaign may count toward your CEP’s event-based pricing. However, we only process the data you choose to send, ensuring flexibility in managing costs.

✔ **Optimized Spend** – Since Verified Campaigns helps reach customers on existing high-engagement channel (Caller ID, Post Call Screen, Message ID), it can complement your existing CEP strategies by reducing dependency on costlier channels like SMS, push, or email—potentially optimizing your overall marketing spend.

**Note:** For specific billing implications related to your CEP contract, please consult your CEP Account Manager or Customer Success teams for appropriate details. 

Please reach out to <cs@truecaller.com> for questions on Verified Campaigns pricing.


---

# 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.truecaller.com/truecaller-for-business/verified-campaigns/faqs/how-will-verified-campaigns-impact-my-ceps-billing.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.