Handling Multiple Contracts with Same Source ID in Campaign

[d001]

Hello,

I hope you are all well.

I have a question regarding the source_id column. I am running a campaign where multiple contracts share the same source_id, and the server regularly calls these contacts. Our client provides us with all their contracts, and our task is to notify their customers. However, in cases where the same source_id appears multiple times, their customers can become annoyed because agents may not realize they've already called them.

I know one solution is to set the status to DNC, but the agents don’t know how many contracts a customer has and can’t set the status to DNC when we’re aiming for a sale.

Does anyone have an idea of how to handle this?

Regards!

[williamconley]

Look up "Auto Alt-Number Dialing: MULTI_LEAD"

You might find it useful.

[d001]

Hello,

Sorry for the late response. The solution you mentioned above works, but only when the source_id is duplicated. We have some additional cases, so we decided to make changes directly in the database using triggers.

I made the server database accessible through phpMyAdmin (someone may use Adminer too), and I created some triggers that fire when the list is active. These triggers will update the status of all duplicated numbers except one and will also count them. Additionally, they will notify the agent about how many contracts are associated with that number and display all the details for each contract.

P.S. Be careful, this may be dangerous if you don't have knowledge of databases. DO NOT MAKE CHANGES IN LIVE OR PRODUCTION. Always test first!