Docs/Sendify Direct and APISendify DirectAPI
Lead Configuration
Primarily for Sendify Direct and API customers. This is where leads arriving from your own system get matched to a representative and an iMessage line.
Who needs this
If an external or custom CRM pushes leads into Sendify and Sendify has to decide who and what handles them, you need Lead Configuration. If your CRM already decides that before the lead arrives, you do not.
GoHighLevel customers
Where it sits in the flow
GoHighLevel comparison
Same destination, different owner of the routing decision. Do not mix the two approaches in one account without a reason, or it becomes hard to tell why a lead ended up where it did.
Distributing volume
Lead Configuration can spread incoming lead volume across your available lines according to the distribution you set up, which is how teams with several lines keep any single line from hitting its daily or hourly ceiling first.
Capacity planning sits alongside this: how many lines do I need covers the daily and hourly numbers you are distributing against.
Configure only what you can see
FAQ
Do GoHighLevel customers need Lead Configuration?
Generally no. GoHighLevel already has workflows and assignment automation that can attach a representative before or while the lead is passed to Sendify.
Does the order of my tags change routing?
No. Tag ordering is not a routing mechanism. If you saw routing change based on tag order in the past, that was a bug, not intended behavior.
Can I split volume across several lines?
Yes. That is one of the main reasons Lead Configuration exists: spreading incoming lead volume across the lines you have available, according to how you set it up.
What if I send the rep or line myself in the API call?
Then you are handling assignment upstream and Lead Configuration has less to do. Use whichever is a better fit for your system.
Still need a hand?
If your volume is going to run past the daily or hourly limits, or something is not behaving the way these docs describe, talk to our team.