Set up for better outcomes.
Connect the context Zig needs for the work you want to do. Start with one useful workflow, then build from there.
Selling more than one product? Create distinct product context and linked ICPs. Use a trusted system or a dated Knowledge Bucket CSV to establish what each customer already owns.
Establish the workspace and its sources
Define the business context+
Settings > Organization
Set the company name, category, website and relevant documentation URLs. The page states that saving a new or changed website URL populates Product and Solution knowledge in the background. Review the resulting material before sellers use it; a website description is not an approved sales promise.
The workspace describes the right business and the product catalog reflects the offerings actually sold. If the organization has multiple business units, avoid using only the parent company's story for all of them.
Give each person the right workspace role+
Settings > Members
Review membership and assign the appropriate Admin or Member role. Decide who owns product knowledge, ICPs, research prompts and rollout changes. Product and ICP sharing is a separate step: membership alone does not prove the rep can see the required resource.
A representative seller can access the correct product and ICP, including Shared with me, and knows who maintains them.
Connect the records needed for the outcome+
Settings > Integrations
Connect the intended calendar, mailbox and CRM using the organization's approved accounts. The inspected UI lists Google and Outlook calendars, Gmail and Outlook Mail, and HubSpot, Salesforce, Pipedrive, Zoho CRM and HighLevel. Configure outreach providers separately. Verify the connection by opening a known account or meeting; an Active badge alone does not prove every required record is available.
A known meeting, contact and opportunity can be found with the right identity and relevant history. Identify any missing fields or historical coverage before promising a complete account view.
Make multiple products usable in selling
Create a distinct source of truth for each offering+
Settings > Product and Solution
Use Add product to define each distinct offering, including a clear name, type, summary and optional website. Add or review sections for capabilities, problems solved, differentiators, implementation requirements, pricing guidance and exclusions. Share each product with the sellers who need it. Distinguish a business unit from its individual offerings when their buyers or use cases differ.
A seller can explain what each product solves and how it differs from the others, without relying on the parent brand's generic description.
Link buyer criteria to the right product+
Settings > Personas and ICP > New ICP
Describe who buys the product before selecting it: industries, size, geography, buyer roles and named examples. The current form warns that a vague description may produce the seller's category rather than the buyer's industry. Generate a draft, then review target companies, buying roles and messaging. Preserve product-specific requirements and disqualifiers. Share both the product and its linked ICP.
An actual suitable account and an actual unsuitable account are classified sensibly for each product. A rep can find both resources and identify the intended offer.
Make current ownership explicit before recommending expansion+
Connected CRM or supplied account context, reviewed in Ask Zig
Choose the source the business maintains for current customer products. It may be CRM, subscription billing, order or contract records, or an internal system accessible through an API. Arrange the connection with the Zig team and verify which records are exposed; API availability is not the same as an already configured integration. Alternatively, upload a dated CSV to Knowledge Bucket and define when Zig should use it. Include customer identity, product, team or business unit, current status and source date. Treat the CSV as a snapshot that needs an owner and refresh process.
A known customer's current products are correct, and an expansion recommendation names a distinct unmet need rather than re-selling an existing product.
Give product recommendations a reliable basis
Write a product comparison brief for sellers+
Product and Solution, Personas and ICP, Knowledge Bucket
For each product, record the problem, suitable company, buyer role, relevant trigger, prerequisites, exclusions and approved proof. Also state relationships between offerings: complementary, overlapping, dependent or intended for different teams. Where a commercial bundle exists, use approved terms. This is an operating recommendation for the guide, not a claim that Zig exposes a dedicated product-comparison settings screen.
Ask Zig to list known products, retrieve a relevant lead list and compare fit using product-linked ICPs, web research and internal conversation data. Check a clear fit, ambiguous fit and existing customer. Verify evidence and coverage before acting.
Supply evidence for the buying decision+
Settings > Customer Proof and Competitive Intel
Review case studies and testimonials for the product, persona and problem they support. Competitive Intel offers discovery, manual competitor addition and battlecards with capabilities, pricing model, where we win, objection responses and discovery questions. Check source dates and relevance before approving claims. Do not interpret generated competitive content as automatically verified.
A rep can retrieve a relevant proof point or comparison and explain its limits. If evidence is missing, the recommended next step is validation rather than a fabricated claim.
Tell Zig when each knowledge item applies+
Settings > Knowledge Bucket, Playbooks, Templates and Sequences
Upload relevant material and choose personal or workspace availability. Knowledge Bucket entries have a title and guidance explaining when Zig should use them. Write that guidance around product, audience, stage and exclusions. Use approved discovery frameworks, messaging examples and stage guidance. The current upload form accepts documents, images and text files; validate the resulting extracted entry.
A draft for Product A uses Product A's positioning and proof. Material for another segment or product is excluded unless there is a clear, explained reason to use it.
Configure research and conversations around decisions
Research the signals that change a selling decision+
Settings > Research
Create company or contact prompts with a heading, plain-language question, personal or workspace scope and refresh interval. Ask questions that help qualify a need or choose a next step, such as relevant hiring, existing technology or an operational change. Require sources and distinguish facts from hypotheses. Review duplicate prompts and disable unnecessary research through the normal settings workflow.
A company research card answers a useful selling question, cites supporting sources and has an appropriate freshness window. Research effort is spent where it can change prioritization.
Prepare and summarize the meetings that matter+
Settings > Meetings
Set ZigScribe behavior for calendar meetings and define Meeting prep focus. Choose a default summary style appropriate to the user's job. Built-in options include Quick Summary, Executive brief, Sales-focused, Action-oriented and Technical deep-dive. Custom styles can support a repeatable discovery or handoff framework. Check meeting classification and per-meeting attendance settings as part of rollout.
An appropriate meeting is captured and produces a usable summary. The brief or recap highlights the next buying decision, commitments and unknowns rather than just retelling the call.
Make follow-ups sound like the seller and serve the deal+
Settings > Outreach
Write Followup guidelines for tone, length, structure, relevant proof and claims to avoid. Configure the waiting period and maximum follow-ups for Chasing a silence. The inspected UI says this workflow drafts follow-ups for review, waits for the user to send and stops when a reply arrives. These rules should not be generalized to every active campaign or automation.
A sample follow-up reflects the real conversation, makes one useful next-step request and respects the configured cadence. Reviewers understand when approval leads to sending.
Make seller execution ready
Set the seller identity and scheduling details+
Settings > Account and Organization
Review the seller's LinkedIn URL and email signature. Organization also exposes a scheduling link used when an email needs a meeting to be scheduled. Confirm it is the appropriate seller or team link. Register recognized phone numbers where voice access is used. Verify the intended mailbox is connected before attempting individual email sending.
A draft has the correct sender identity, signature and meeting link. A booking link is not evidence that a meeting has already been arranged.
Prepare phone conversations and callbacks+
Settings > Dialer and Calls
Confirm the provisioned number, incoming-call behavior and outgoing caller ID. Incoming calls can ring in the browser or forward to a phone. Review recording preferences and the organization's recording process; the page notes that recording consent obligations vary. Recorded calls can support transcripts, summaries and follow-up drafts. Do not place a test call to an unsuspecting prospect.
Use an agreed internal test to confirm ringing or forwarding, caller identity and recording behavior. A completed test has a usable record and the expected follow-up path.
Capture the event information that qualifies a lead+
Settings > Scanner Properties
Choose which CRM contact fields appear during badge capture and which are required. Include the information that helps determine fit or follow-through, such as product interest, buying role or a concise qualification field available in the CRM. Keep the required set short enough for live event use. Confirm field mapping and save behavior through an agreed test.
A test badge or contact preserves identity, useful qualification context and the promised next step, and reaches the right event list or CRM destination.
Turn inbound signals into relevant sales work
Choose a source and a qualification policy+
Automations > New automation > Configure
The UI offers Zig Pixel, RB2B and inbound webhooks. CRM, PostHog and Stripe event triggers are labeled Enterprise only. Choose the intended source, then define target ICPs and additional criteria. Leaving ICPs empty accepts every visitor. Resolve identity when the source supplies only an email, domain or IP and qualification needs company or contact facts. Review the credit implications.
An agreed sample lead produces the intended qualification result, and a poor-fit sample is rejected or routed appropriately. Do not describe a listed Enterprise trigger as enabled until access is confirmed.
Route qualified leads without conflicting outreach+
Automation Configure > Enrichment, Find Contacts and Route
Decide whether to skip contacts already in CRM or already in a sequence. Enable company research where routing needs evidence. Choose whether to route the inbound visitor or find relevant buying-committee contacts at the qualified company. Define ordered segments: the first matching segment wins. A segment can add leads to a list and enroll them in selected campaigns; multiple selected campaigns enroll simultaneously.
Each sample lands in the intended product-specific group. Catch-all behavior is deliberate, and existing customers are not accidentally treated as new-product prospects without checking what they own.
Test delivery and monitor the full funnel+
Automation Test with sample lead and Activity
Review sample behavior before enabling a new automation. Confirm destination lists, campaigns and channel readiness, then inspect actual activity after launch. Compare received, qualified, routed, added and enrolled outcomes. Trace missing identities or failures rather than assuming every qualified record reached a seller. Live, paused and draft states should be part of the operating review.
A qualifying record reaches the intended destination and produces the expected seller action. Received, added-to-list and enrolled counts are treated as distinct events.
Make recurring work sustainable
Connect outreach and manage the operating limits+
Outreach, Integrations, Usage and Billing, Notifications
Confirm the intended Instantly or Smartlead account for email campaigns and HeyReach access for LinkedIn. Check sending-account readiness separately from drafting. Review available enrichment credits, email capacity, dialer minutes and LinkedIn allowance in the workspace's current plan. Configure credit-alert recipients and personal email notifications. Avoid hard-coding plan limits in the general guide.
A seller can prepare the right campaign and explain whether it is drafted, launched or blocked. The team has an owner for credit alerts and capacity issues.
Prove a reusable workflow before scheduling it+
Settings > Skills and Schedules
Zig can run recurring account reviews and identify new actions. Define the account scope, cadence, evidence sources and expected decisions, then validate one manual review. Configure the schedule owner, time zone and destination session. A workspace schedule starts one run for every person as that person, so confirm scope. Check that each run reports material changes, proposed next actions and missing evidence. Recurring analysis does not establish that a proposed action was executed.
The workflow works on a bounded dataset and a scheduled run produces the expected output under the correct user's access. Missing data is reported instead of silently treated as zero.
Enable the intended working surface and ownership+
Settings > Connect Zig and Organization
Connect Zig exposes an MCP server connection for compatible assistants and API keys for webhook authentication. Grant only the access approved for the intended workflow, and keep keys out of guides and example prompts. Organization also contains the Zig Advisor channel destination. Name the person who maintains the guide, validates product changes and resolves workflow failures.
The chosen working surface can access the intended records, and users know who to contact when a workflow or source is unavailable.
Review opportunity proposals from meetings
When the customer expresses interest in moving forward, or Zig judges that a conversation could progress positively and is not disqualified, it presents a human review card on Today and the meeting summary page.
Creating or updating an opportunity requires human review. Check the proposal against the conversation, then confirm the outcome of any approved action.
Use a CSV for product ownership
Upload a dated CSV to Knowledge Bucket with customer identity, product, business unit, current status and source date. Define when Zig should use it, who refreshes it, and whether missing rows mean no ownership or incomplete coverage. API-based internal systems can also be connected with the Zig team.