Guides and answers for everything Signalist – searchable, and always up to date.
Build with the Signalist API & MCP – reference, guides and examples.
Get instant, sourced answers about Signalist from our AI.
Stuck on something specific? Talk to a human on the team.
This walkthrough helps you reach the smallest safe first result in Signalist. You will check the essentials, choose a suitable lead source, build a small test list, review lead quality, and reach the message review stage.
This article walks you through verifying users, permissions, connected accounts, and campaign senders step by step.
Clear responsibility helps prevent duplicate outreach, missed replies, unsafe activation, and unclear decisions. If your team uses lists, campaigns, trackers, or replies without named owners, it becomes easy for the same person to be contacted twice, for a campaign to be activated without a final check, or for replies to sit unanswered.
Tracker lists are the collections of companies Signalist watches for you. Every signal we detect is matched against your lists.
Signalist syncs with HubSpot, Salesforce, Pipedrive, Zoho and Microsoft Dynamics. Connect once and signals flow into the tools you already use.
Choose your list source by starting with what you already have and what you want the list to do next. If you begin with the source name alone, it is easy to pick something too broad, too narrow, or not available in your workspace.
LinkedIn activity can help you build timely lists from profile visits, followers, events, posts, engagement, or prepared LinkedIn URLs. Use the source that matches the specific signal, then qualify the people before you treat them as outreach candidates.
Use AI Company Search to describe target companies in natural language, and use news or signal monitoring to watch for specific events. Both work best when your prompt is verifiable, your exclusions are explicit, and each result has a defined review or follow up action.
Use an XLSX upload when you already have a defined set of people, companies, or job titles. A clean file and a careful preview help Signalist match the right records and reduce avoidable duplicates, credit use, and manual correction.
Create an event list from the most reliable input you already have: a prepared file, a supported LinkedIn event, or a clearly scoped request to the Scraping Service. Choose the route first, then qualify the people or companies before planning outreach.
Manage duplicates and blacklists as part of the team workflow, not as a single cleanup step. The same contact can legitimately appear in more than one list, but outreach becomes unsafe when ownership, campaign status, previous replies, opt outs, or exclusion rules are ignored.
Use jobs, job changes, funding, mergers and acquisitions, and re engagement as reasons to review an account or contact. These events can create useful context, but none of them proves buying intent on its own.
Use Copywriting settings for shared style and delivery rules, and use Templates for reusable prompts, replies, and Deep Research instructions. Each campaign still needs the correct list, signal, persona, language, and sender context.
Review every Knowledge DB section before approving it for research or copywriting. Approval means the content is trusted enough to influence customer facing output, so persuasive wording is not a substitute for accurate evidence.
Write Deep Research prompts around a decision: qualify an account, verify a signal, identify the relevant role, or find a factual conversation angle. A focused prompt produces more useful results than an open ended request to research everything.
Use P1, P2, P3, and DQ to make consistent review decisions—not as automatic truth. A priority is useful only when the team shares a definition and checks company fit, persona fit, source evidence, and the next action together.
Configure lead scoring by separating company fit, persona fit, and hard exclusions. This keeps results easier to explain and helps reviewers understand why a lead qualifies, receives a priority, or is disqualified.
When sending stops, do not restart or duplicate the campaign immediately. Record the affected list, lead, status, sender, channel, and expected time, then check one layer at a time.
Use List to choose the right work queue and Review to inspect one lead, its context, and the prepared sequence. A qualified lead is not automatically ready to send.
Use Inbox to manage replies and Outbox to inspect Sent and Scheduled activity. Clear ownership and consistent filters prevent missed replies and misleading delivery checks.
Confirm the connected sender, recipient email status, domain policy, limits, delays, sequence, and schedule before email activation. A found email address is not automatically send ready.
Protect the LinkedIn account by prioritising audience quality, conservative volume, natural delays, and review. Treat limits as safeguards, not targets.
Create a campaign only after the list, hypothesis, recipients, owner, and exclusions are clear. Then configure copy, sender, channel, sequence, limits, delays, and timing before a controlled activation.
Process the Signal Feed with a consistent daily ritual: review New, verify evidence and fit, move uncertainty to To be reviewed, assign clear work, and ignore irrelevant signals with a reason.
Use a Company Tracker when selected accounts or people should be checked repeatedly for relevant changes. The tracker creates value only when prompts, priorities, review cadence, ownership, and next actions are maintained.
Configure signal scoring so the team can distinguish person, company, and market context and apply P1, P2, P3, and DQ consistently. Use definitions with positive, negative, and boundary examples.
Create scoped API access, protect keys like passwords, and test webhooks with non sensitive data.
Compare the same period, list, sender, channel, and campaign before drawing conclusions from activity and replies.
Filter the correct Contacts view, select only needed columns, and export a reviewed dataset to protected storage.
Connect a supported CRM and validate authentication, user mapping, and field delivery with one controlled test.
Define object, owner, trigger, fields, and deal behaviour before connecting a CRM.
Plan credit use by workflow and review plan, invoices, payment options, and sender capacity in Plans & Billing.
1. State your goal in one sentence. 2. Name the app area, list or campaign, and visible status. 3. Record expected and actual behaviour plus exact time and timezone. 4. List the last safe steps before the problem. 5. Attach a redacted screenshot only when it adds evidence. 6. Send the request through the approved support channel and avoid parallel changes during critical sending investigations.
Mirrored from Signalist Brain. Edits made here are overwritten the next time the article is published — edit it in Brain.