Tracking, QR & Attribution
Can Sales Be Alerted When a Prospect Scans?
Yes. A scan tied to a specific account or recipient can trigger a live alert to email, Slack, a CRM record or another connected workflow, often within seconds of it happening. The value isn't the notification itself, it's giving the sales team enough context to reach out while the postcard and the message are still fresh in the recipient's mind.
Practical guide · Published August 22, 2026 · Written by Jeffrey Huis in 't Veld
What "real time" actually means
In practice, this means the alert can land within seconds to a couple of minutes of the scan happening, not bundled into a report the next morning. That speed is the entire point: a prospect who scanned a postcard five minutes ago still remembers what it said and why they picked up their phone. The same prospect a week from now, reading a summary buried in a weekly report, is a much colder conversation to restart.
What the alert should contain
A useful alert identifies which account or recipient scanned, which campaign and which specific postcard they received, and where they landed afterward. Without that context, an alert is just "someone did something," which isn't enough for a salesperson to have an informed conversation. With it, the salesperson can reference the actual piece the prospect received, which is a much stronger opening than a generic "I saw you visited our site."
Where the alert goes
Common destinations are a direct email or Slack message to the account owner, a task or activity logged automatically on the CRM record, or both. Which one makes sense depends on how the sales team already works. A team that lives in Slack during the day gets more value from a Slack alert than a CRM task that might not get checked until later. A team running a structured pipeline process may prefer the CRM record as the source of truth, with Slack as a secondary nudge.
Avoiding alert fatigue
Not every scan deserves an interrupt-level alert, and treating them all the same way is how a team starts ignoring the channel entirely.
| Event type | Example | Suggested handling |
|---|---|---|
| High-value or named account scan | A Tier 1 strategic account engages | Immediate alert to the account owner |
| Repeat engagement | Same recipient scans again within days | Immediate alert, flagged as renewed interest |
| Broad-list, lower-tier scan | A Tier 3 first-touch list engages | Batched into a daily or weekly summary |
| Non-human activity | Preview crawlers, automated link scanners | Filtered out before it reaches sales at all |
What sales should do with it
The strongest response references the specific piece the prospect received rather than opening with a generic pitch, since that's what makes the follow-up feel like a continuation of a conversation the prospect already started, not a cold outreach that happens to have good timing. This is easiest when the personalization used on the mailer, the message, the imagery, the specific offer, is visible to sales at the moment of the alert, not just to the marketing team who built the campaign.
Setting this up before launch
Routing rules, who owns which accounts, which events warrant an immediate alert versus a batched one, and what integration is actually in place should all be settled before the first postcard goes out, not figured out after the first scan already happened and nobody was sure who should respond. A campaign that generates engagement with no clear owner on the other end wastes the exact moment it was built to capture.
What a scan doesn't tell you
A scan is an engagement signal, not proof of purchase intent. It means someone was curious enough to act, not that they're ready to buy. Sales still needs to interpret the signal in context, who the recipient is, what they landed on, and what a reasonable next step actually looks like, rather than treating every scan as a hot lead ready to close.
Frequently asked questions
With the integration set up correctly, typically within seconds to a couple of minutes. The delay usually comes from how the destination system is configured, not the QR technology itself.
This depends on what a specific team already uses and what integration is supported for that stack. The core requirement is a workflow that can receive a triggered event and route it to the right owner.
No. Reserving immediate alerts for higher-value or named accounts, and batching lower-tier engagement into periodic reports, keeps the signal meaningful instead of becoming background noise.
No. It means they engaged with the piece enough to act. That's a useful signal to follow up on, not evidence of purchase intent on its own.
The alert loses most of its value. The entire advantage of real-time routing is a fast, informed follow-up, so ownership and response expectations need to be clear before the campaign launches, not left to whoever happens to notice.
Related topics
Work with Yotru
How Yotru's live scan alerts actually work
Yotru ties each unique QR code to the specific account or recipient it was printed for, so when it's scanned, the alert we route to email, Slack or your CRM carries the account, the campaign and the exact piece they received, not just a bare notification that a scan happened. We also help set routing rules by tier before launch, so a Tier 1 account triggers an immediate alert while broader-list engagement can batch into a periodic summary instead of burying the team in noise. .