Custom Tools for AI SDRs and Campaigns — Let the Bot Check Before It Sends

Bharadwaj Giridhar's profile pictureBharadwaj Giridhar
3 min read

Summary

Tuco’s custom tools let teams connect outside systems to AI workflows once, test them on a real lead, then reuse them in campaigns, AI SDR stages, stop rules, and per-message prompting.

Send iMessages from your CRM—higher response, fewer blocks

Connect Salesforce, HubSpot, GoHighLevel, or Clay. Deliver to iOS users without carrier throttling or filtering.

Custom Tools for AI SDRs and Campaigns

AI workflows get much better when they can ask one more question before they act.

Does this lead already have an open ticket? Is the account in the right lifecycle stage? Did finance approve the offer? Is inventory still available?

If your workflow cannot answer those questions, the bot either guesses or sends the wrong thing.

What custom tools are for

Tuco lets you build a reusable custom tool once at the workspace level, test it on a real lead, and then reuse it anywhere the workflow needs outside truth.

That includes:

  • prompt-built campaigns
  • per-message prompting inside campaign steps
  • AI SDR stages
  • stop conditions
  • branches and routing logic

Reach leads on iMessage, not just SMS

Outbound iMessages from Salesforce, HubSpot, GoHighLevel, Clay. Higher response, no carrier throttling.

Why this matters for AI SDRs

An AI SDR should not qualify in a vacuum.

Sometimes the best next question depends on what another system says. Maybe the lead has already booked. Maybe they are already assigned to another owner. Maybe their account size changes which offer should show up next.

Custom tools let the AI SDR check before it decides.

Why this matters for campaigns

Campaigns are no longer just timed messages. In the dev product, each message can be prompted individually, and those prompts get more useful when the bot can pull in real context from outside systems.

Instead of:

“Send the same generic step to everyone.”

You get:

“Use the result of this tool call to decide which message to send, whether to stop, and what the prompt should say.”

Test on a real lead

This is one of the underrated parts of the feature.

You do not have to imagine whether the placeholders or mappings will work in production. You can test the tool on a real lead record before it ever touches a live workflow. That makes it much easier to trust the result inside:

  • stop checks
  • branching logic
  • AI-generated replies
  • AI SDR qualification paths

Better than rebuilding logic everywhere

Without a reusable tool layer, teams end up duplicating the same external check in multiple places. One version in a campaign. Another in a webhook. Another in a bot prompt. Then the logic drifts.

With custom tools, the workflow can call the same saved check everywhere it matters.

The practical outcome

The bot becomes less “creative” and more useful.

It knows when to:

  • stop before a bad send
  • branch to a different offer
  • ask a sharper qualification question
  • route a revived lead to the right owner

That is the difference between AI copy generation and AI workflow execution.

See the custom tools feature page, see AI SDRs, or book a demo.

About the author

Bharadwaj Giridhar's profile picture

Founder at Tuco AI. Helping teams turn iMessage into a real workflow layer.

See Tuco in action

3x higher reply rates than email

Get Started
Get StartedMini self-serve, Growth demos