Routing, queue & bridges
Once you have messaging pipelines, three things make them work end to end: router conditions decide which pipeline a queue item goes to, the queue shows every message waiting to send or already sent, and data bridges automatically pull recipients in from your own server. Together they turn the transactions and recipients you send into the right messages, delivered reliably.
This is the operational heart of messaging — where targeting rules meet real delivery.
Router conditions
Router conditions decide which pipeline each queue item flows into. You build them with full AND/OR/NOT logic over questionnaire metadata and responder metadata, and you can import many at once from a spreadsheet. See Router conditions for the full guide.
The dispatch queue
The queue is your outbound message list — every invitation waiting to send or already sent, shown 25 per page and sorted by send time. Each row carries the recipient, the survey and pipeline, scheduled and sent times, language, a status that tells you what happened, and a source that shows how it got there. You can add recipients by hand or by CSV, open any item, edit or abort pending ones, and reschedule an item or reset it so it's sent again.
Data bridges
A bridge automatically loads recipients from a file on your SFTP or FTP server into a pipeline on a schedule — so a list your systems export is surveyed without anyone uploading anything.
Go deeper
Router conditions
Decide which pipeline each queue item flows into with AND/OR/NOT rules.
The events router
Route transactions from your own systems to the right survey and pipeline.
The dispatch queue
Queue-item settings, every status and source, the actions you can take, and how imports work.
Data bridges
Connect to your server, map columns, schedule runs and test the connection.
From here, results flow onward to Insights, and you can chain a follow-up with sequences.