Short answer
Yes. With FirstNet Truecaller for Business, static call reasons such as "Payment reminder" or "Delivery update" are set per number or use case at onboarding and suit most outbound teams. Dynamic call reasons are sent at dial time from your CRM, dialler or contact-centre platform, so each call can carry a customer-specific or campaign-specific reason.
In detail
How the two options compare:
- Static reasons: a small set mapped per number or use case, enough for most collections, delivery and appointment calls. FirstNet changes them on request.
- Dynamic reasons: your system passes a per-call reason through the Truecaller API or a webhook, with end-to-end authentication.
- Typical dynamic uses: personalised collections, claim-specific updates and campaign-specific messages.
- Integration: dynamic reasons are scoped as an integration project, with a technical workshop for complex or large deployments.
The recommended starting point is static reasons on one or two priority numbers, measured in a pilot, with dynamic reasons added where the business case is clear.
Keep reasons short and relevant, and consider whether a reason could reveal personal details on a recipient's screen, because call-reason content shapes POPIA outcomes. The analytics dashboard shows how answer rates change as reasons are refined.
Source: FirstNet Truecaller for Business service page →
Didn’t answer your question?
