Leverly MCP integration

Create Call sends the lead's information to Leverly, which triggers an instant phone call to your sales team rather than filing a record for later follow-up. Because it puts a rep on the phone, it belongs at the end of a qualifying conversation, not in a routine lookup.

No. The toolkit exposes Create Call, List Reattempts, and Stop Leverly Reattempts, and none of them return a call outcome, duration, or recording. Ayro can confirm a call was created and read the reattempt history, but what was said lives in Leverly and whatever your reps log afterwards.

Stop Leverly Reattempts acts on a specific reattempt ID, so Ayro has to run List Reattempts first and identify the right one. There is no action that halts everything at once, which keeps a mistaken stop scoped to a single lead rather than the whole queue.

A Zap fires on every form submission in the same shape. Ayro talks to the person first, so it can judge whether the lead warrants a call, create it carrying the context from that conversation, and later stop the retries if the same person says they have already been contacted.