Skip to main content
This is the risk Nudge is built around. Personal numbers are paced automatically: a gap between sends, hourly and daily caps, and working-hours gating. The pacing is what keeps a rep’s line looking human, so keep broadcast-shaped traffic off it and shrink your segments instead. A Cloud API number carries conversations without that pacing, and with an approved template it can also send cold outreach outside Meta’s 24-hour window. See WhatsApp.
Automation stops for that contact by default. Queued automated messages are cancelled and the conversation continues in the Inbox with a human. How long the pause lasts is a setting, and an individual trigger can opt out of it, which is what you want for something like a callback the contact asked for.
No. A trigger fires once per contact, ever. Editing the trigger resets this deliberately, so a corrected message can reach the audience again. The one exception is a trigger that reacts to call outcomes: if the same contact calls or is called again after 30 quiet days, it treats that as a fresh conversation and the retry chain can run once more. That is what you want — someone who comes back months later should not be met with silence because a rule already fired in the spring.
Nudge holds the message rather than send the wrong language. A template with no language tabs is treated as language-neutral and goes to everyone.
No. Nudge runs standalone with its own contacts, deals and forms, or on top of your HubSpot with two-way sync. See HubSpot mode.
Yes. Every contact page has a Skip automations toggle.
A fictional solar installer with 200 fake contacts, live triggers, and simulated calls and messages. No real messages are sent, and everything resets nightly. Open it at demo.nudgecrm.dev.
Request a demo at autonudge.dev. Each customer gets a dedicated instance, set up for you, usually within days.