Skip to main content

Documentation Index

Fetch the complete documentation index at: https://support.artisan.co/llms.txt

Use this file to discover all available pages before exploring further.

Yes. All campaign settings can be changed after launch.When a change affects how Ava writes or sends messages, Ava will ask how you want to apply it:
  • Apply to all leads including in-flight: leads already in progress will get the updated changes.
  • Apply to new leads only: leads already in progress will not be affected.
This lets users safely update a live campaign without recreating it.
Choose whether Ava should send messages automatically or wait for approval.
  • Autonomous mode: Ava writes, personalizes, schedules, and sends messages without asking for approval. This is the recommended default because users do not need to keep logging in to approve messages.
  • Review mode: Ava drafts each message, but the user must approve it before it is scheduled to send. This is best for a user’s first few days on a new campaign type, or for regulated industries where every message needs sign-off.
In review mode, messages waiting for approval appear on the Tasks page under the Scheduled tab. If pending messages are less than 4 hours old, the user is keeping up. Anything older means the queue is backing up.
Set the number of new leads Ava should start outreach to each month from this campaign’s audience.This is the campaign’s monthly volume cap. Ava stops when she reaches this number, even if more people are available in the attached lists. This number also determines the campaign’s monthly credit cost.
Add the people Ava will send messages on behalf of.Each sender should have at least one connected mailbox. For best results, connect their primary mailbox, secondary mailboxes, and LinkedIn so Ava can send at full speed.Click a sender’s row to connect accounts and set location, timezone, and past experience. Ava uses this information to time outreach and personalize messages.Every sender added to the campaign gets full read and edit access unless Campaign access is turned off on the Settings → Access Control page.
Turn this on if you want Ava to reply to leads without needing approval each time. Ava can answer objections, handle clarifying questions, and, in meeting-booking mode, help book meetings.There are 2 ways Ava can handle replies:
  • Handling objections only: Ava handles common replies like objections, pushback, and clarifying questions, but does not book meetings.
  • Handling objections and booking meetings: Ava handles objections and guides qualified prospects toward booking a meeting.
Knowledge base: Add sales decks, case studies, product docs, and other company materials so Ava can answer questions and handle objections accurately.Escalation rules: Set when Ava should stop replying on her own and route the conversation to a user instead. There are two layers:
  • Global escalation rules: org-wide rules. Inherited by default. Two locked rules always apply: “If the lead asks to unsubscribe or opt out” and “If Ava is unsure or missing required context.” Other global rules can be added at the org level.
  • Custom escalation rules: campaign-specific additions on top of the global set. Use these for campaign-level scenarios that don’t apply org-wide (e.g., “escalate if the lead mentions a specific competitor we’re tracking against on this campaign”).
Reply coaching: Add guidance for how Ava should write when replying to prospects.Qualification criteria: Define what makes a lead worth booking a meeting with. Ava first uses web research to check whether the lead meets the criteria. If she cannot find the information online, she asks the lead qualifying questions in the thread before sending the booking link.Shareable resources: Add assets Ava can share when prospects ask for more information, such as one-pagers, case studies, demo videos, and product docs. Ava chooses the most relevant resource and includes the link in her reply.
This setting lets Ava re-enroll leads who do not respond after a set cooldown period. The default cooldown is 90 days, and re-enrollment can repeat a configurable number of times.This is not a trade-off against contacting new leads. Both happen in parallel. You keep working through a fresh audience while also reaching back out to past non-responders when their cooldown ends.
We recommend including an unsubscribe option for 2 reasons:
  1. It helps you follow CAN-SPAM, GDPR, and CASL rules, depending on where your prospects are. Mailbox providers also increasingly expect cold outbound emails to include an unsubscribe option.
  2. Plain-text unsubscribe wording keeps the option low-key and avoids a large unsubscribe button. The “Let Ava choose” option varies the wording across messages, which helps protect deliverability because spam filters can flag identical opt-out phrases used at scale.
Use DNC (do not contact) rules to prevent Ava from contacting people you want excluded from outreach. There are five optional layers:
  • Exclude from CRM: pull in CRM records (contacts, leads, accounts, opportunities) and exclude any prospect that matches.
  • Exclude from Artisan lists: select from a list of existing Artisan lists. Any list you upload to a campaign or from the Lists page can be accessed from here.
  • Contact recency exclusion: exclude prospects who’ve been contacted (by any campaign in the org) in the past 30 days. The number of days is configurable.
  • Domain exclusion: exclude prospects whose email matches any of a list of domains (useful for blocking competitor companies, existing customer domains, partner domains).
  • Max people per company cap: limit how many prospects from the same company get contacted in this campaign.
All of these layer on top of the org-wide global DNC, which is always inherited.
Choose what Ava should prioritize when daily sender capacity is not enough for both new outreach and pending follow-ups. Three options:
  1. Balance new outreach and follow-ups: The recommended option. Ava reserves capacity proportionally for both.
  2. Prioritize reaching out to new contacts: Ava focuses sender capacity on first-touch emails. This can improve reply rates because first-touch emails typically perform better than follow-ups.
  3. Prioritize follow-ups: Ava continues existing conversations before starting new ones.
These rules decide which sender owns each prospect. Once Ava assigns a prospect to a sender, that sender stays with the prospect for the full sequence and any replies.Users can drag to reorder rules, change priority, or remove rules entirely.There are five rules in priority order:
  1. Lead owner on CRM: if the prospect is already a Lead in your CRM with an assigned owner, that CRM owner’s mapped Artisan sender takes the prospect. Requires the CRM owner to be mapped in the CRM owner mapping table.
  2. Account owner on CRM: if the prospect’s company is in your CRM as an Account with an owner, that owner’s mapped sender takes the prospect.
  3. Lead owner on Artisan: if the prospect is already in Artisan with an assigned sender from a previous campaign, that sender keeps them.
  4. Account owner on Artisan: if the prospect’s company is already in Artisan with an assigned sender from a previous campaign, that sender keeps them.
  5. Round robin between all senders: anyone left over gets distributed across the campaign’s senders. The split can be done either by capacity (round robin proportional to each sender’s available capacity) or by pure round robin (equal split).
These settings control how Ava handles replies based on sentiment: positive, neutral, or negative.
  • Stop the sequence: By default when a user replies (regardless of sentiment), Ava stops sending further outreach. However, if autonomous replies are turned on, she will reply to the message depending on the rules.
  • Notify in Slack: Configures whether and how a Slack notification fires for each reply sentiment.
Choose which mailbox pool Ava should use for the selected senders. For cold outbound campaigns, we recommend using secondary mailboxes and reserving primary mailboxes for warmer, relationship-based outreach.
  • Use primary mailboxes: emails that end with the company’s actual domain. Higher trust, but using them too aggressively for cold outbound risks hurting the primary domain’s reputation.
  • Use secondary mailboxes: emails on a similar-but-different domain. Lower trust per individual send, but isolates the cold outbound load from the primary domain so deliverability issues don’t cascade onto real business email.
Both settings are designed to protect sender reputation and overall deliverability. Bounces and spam complaints can damage every campaign’s deliverability across that domain.
  • Bounce test email addresses: validates every email address before sending. Adds a small per-check credit cost. Catches invalid, mistyped, or no-longer-active addresses before they trigger a hard bounce.
  • Exclude email addresses marked as risky: skips addresses that are flagged as risky (e.g., catch-all domains, role-based addresses like info@, addresses with suspicious patterns). Risky addresses are more likely to bounce or generate spam complaints.
Set when Ava should send sequence emails.
  • Daily sending window: start time and end time. Default 9:00 AM to 5:00 PM. Ava only sends inside this window.
  • Timezone: “Lead’s timezone” (default) or a specific fixed timezone. Lead’s timezone means each prospect receives emails during their local working hours.
  • Send on weekends: Toggled off by default. Ensures no sends on Saturday or Sunday.
  • Dates Ava should avoid sending messages on: blackout dates that you can add (e.g., major holidays, company-wide blackouts, regulatory windows).
  • Send as new thread: Each follow-up appears as a separate email, giving it fresh visibility in the inbox.
  • Send in same thread: Follow-ups stay in the original thread, preserving context but getting less individual attention.
Continuing outreach while someone is OOO usually hurts reply rates because messages pile up unread.This setting is on by default. When it is on, Ava detects out-of-office auto-replies and pauses the lead’s sequence until they are back. There are two paths:
  • Return date detected: If the OOO auto-reply specifies a return date (e.g., “I’ll be back on May 5”), Ava pauses until that date and resumes the sequence after.
  • No return date detected: Ava falls back to a configurable fallback period (default 14 days) and resumes after that.