Share surveys with links, contacts and campaigns

Recommended workflow

Contacts and audiences

Contacts are useful when you know who should receive the survey, when you need personalized links, or when the survey should use contact fields such as name, email, organization or custom data.

You can import contacts from a spreadsheet, a CSV, a pasted table or another tool. Dayalogs recognizes common fields like name, email and phone automatically and keeps anything else as extra data, so nothing from your original list is lost. Each import can be tagged, and also gets an automatic tag so you can always find that batch again later.

• Use tags to keep imports and target groups easy to filter.
• Use segments to build dynamic groups from rules, such as everyone tagged clients above a certain age.
• Use contact data when the survey needs to display or branch on respondent-specific information.
• Use manual contact selections for small, controlled sends.

Inside a survey, contact values can be referenced through @contact, which means personalized links can drive both delivery and respondent-specific survey behavior.

Links and LinkSets

A LinkSet is a managed group of links for one survey. It can represent a partner list, a recruitment channel, or a set of personalized respondent links. Sending those links by email is a separate campaign operation.

LinkSets can also be exported when Dayalogs is not the sending tool. This is useful if you want to load personalized links into Mailchimp or another provider, hand them to a partner, or simply download a batch of links for testing and QA.

A new LinkSet creates new links by default. Reusing unused links is a separate option, and only makes sense when you want to avoid generating a second URL for the same contact while preparing the send.

Quotas, dates and status

Links and LinkSets can be limited without changing the survey definition. That makes it possible to stop one channel, cap one partner, or pause a campaign without reimporting the survey.

• Manual status opens or disables a link or LinkSet.
• Activation dates define when a link should start and stop accepting responses.
• Quota limits cap completed responses, either globally for the LinkSet or per reusable link.

Survey-level quotas are separate. Use them when the quota depends on answers or respondent data, not on the link itself.

A campaign turns a LinkSet into an email send. It controls the sender, subject, email body, disclaimer, template and delivery workflow.

• Campaigns should target LinkSets that contain recipients.
• Sent campaigns become an audit record and should not be freely edited afterwards.
• Draft or archived campaigns can be cloned when you want to reuse a structure without touching the original send.

You can personalize each message with placeholders so it greets people by name and includes their own survey link. If you forget to add the link, Dayalogs adds a button automatically, so no invitation goes out without a way to reach the survey.

Sending safely

• Send yourself a test email first to check the wording, the links and how it looks.
• Real sends stay blocked until the survey is collecting responses, so you never invite people into a survey that is not open yet.
• For larger lists, Dayalogs sends a small warm-up batch first and then the rest. This protects your sender reputation and gives you a final chance to review before the full send.
• Each recipient shows a clear status — pending, queued, sent, failed or skipped — so you can follow how the send is going.

If you already use another email platform, you can still use Dayalogs to generate links and export them.

Common examples

Newsletter or website survey

Create one anonymous link, optionally add a source variable, and place it in a newsletter, website, social post or QR code.

Customer satisfaction after a service

Import contacts, generate one personalized link per customer, and send a campaign that greets each person by name.

Company survey through department managers

Create one reusable link per department. Managers can share their department link with their teams, while Dayalogs and you still know which department each response came from.

Working through admin or MCP

Dayalogs treats the admin interface and MCP as two ways to reach the same operational state. You can build the setup manually in the dashboard, or ask an MCP-connected AI client to create contacts, prepare LinkSets, generate links, inspect campaign readiness and explain the current fieldwork setup.

This is useful when your audience source is messy: an Excel file, a pasted list, a CRM export, or instructions like “create one reusable link per department and prepare an email campaign for each manager”. The AI client can transform the input into Dayalogs contacts, tags, LinkSets and campaigns, while Dayalogs remains the system of record.

For sensitive operations such as sending campaigns, deleting records or changing live collection settings, Dayalogs keeps permission checks and confirmation flows in place. MCP does not bypass account permissions; it uses the same product rules as the admin UI.

Quick reference