FAQ

Pamphlet is built for outbound-led revenue teams that need CRM, sequences, inbox replies, Pam AI research, and Pam Agent automation in one workspace instead of a patchwork of point tools.

Pamphlet does not publish list pricing on the marketing site. Book a demo to review packaging for your team size and outbound motion.

Start with feature pages and comparison articles for tools you use today, then book a demo to walk through research, campaigns, inbox, and Pam Agent on your workflow.

Yes. Organizations create separate Pam Pods per team or motion and use Pam OS to monitor portfolio health when more than one Pam Pod is active.

Pamphlet uses Clerk for sign-in and organization membership. Workspace access respects org and Pam Pod boundaries configured in your account.

API keys are created in security settings with bearer authentication scoped to a Pam Pod. Keys can be rotated and revoked without affecting unrelated workspaces.

Yes. Sending policy includes emergency stop, which halts outbound mail across the Pam Pod until an authorized operator resumes sending.

Privacy and terms are published at /legal/privacy and /legal/terms. Contact cs@pamphlet.io for security or data processing questions.

Pam AI produces research, drafts, and evaluations for human review. Pam Agent pursues objectives with tool calls and optional sends, recording each run for audit.

That depends on sending policy and approval settings. Many teams require review for agent sends, and emergency stop applies to automated mail as well.

Agent runs show objective, status, tool call count, and send count. Pending approval requests list actions awaiting operator review.

Yes. The Pamphlet MCP server lets MCP-compatible clients use Pam Pod tools with a scoped API key and Pam Pod ID from developer settings.

Pamphlet provides a native inbox for conversation threads tied to CRM records. Many teams handle outbound replies inside Pamphlet while keeping personal mail elsewhere.

Quarantine holds messages that fail deliverability or policy checks so operators can inspect them before release or discard.

Yes. Pam AI generates reply drafts and supports evaluation flows so operators review suggestions before sending from the inbox.

Use mail health, send queue, and domain settings inside the Pam Pod. Sending policy controls volume and timing to reduce deliverability risk.

Chat projects run on your site to answer questions, collect qualification data, and create transcripts operators review in the Pam Pod workspace.

Qualified sessions can link to prospect, contact, and deal records so inbox and outbound teams continue the motion with full context.

Intent assessment interprets visitor goals from chat answers and signals. It helps operators prioritize follow-up without reading every transcript manually.

Yes. Transcripts store the full session history for review, training updates, and handoff to human operators.

Yes. Pamphlet stores accounts, contacts, prospects, deals, conversations, and campaign activity in your workspace database. Empty states appear when records do not exist yet.

Yes. Prospect import brings external lists into a Pam Pod for research, sequencing, and tracking against inbox and deal outcomes.

Pam Pod knowledge settings ground Pam AI research and drafts in your approved context so outputs reflect your product and policy boundaries.

REST API v1 and webhooks support integrations with your data warehouse or other systems. See developer settings and /developers for documentation entry points.