What is Gork mail (also searched as Grokmail or gork.email)?

Gork mail (gork.email, often spelled Grokmail or Grok mail) is programmable email infrastructure designed specifically for AI agents, LLMs, and autonomous workflows. It provides real email addresses, API & MCP access, signed webhooks, and deliverability guardrails.

How does Gork mail work for AI agents?

Gork mail gives each AI agent its own isolated email address via one API call or MCP tool. Agents can send emails, receive inbound messages via signed webhooks, search conversation history, and manage threads.

Can I use Gork mail with Claude Code, Cursor, or LangChain?

Yes. Gork mail ships a native Model Context Protocol (MCP) server. Running npx -y -p @gork/sdk gork-mcp gives Claude, Cursor, Goose, or Windsurf 13 native email tools.

Back to all blueprints

Templates · Sales & Growth / Autonomous Sales Development Representative

AI Sales / SDR Agent (Outreach & Objection Handling)

Sends targeted outreach, understands prospect replies, qualifies intent, and books demos.

Create handle All blueprints

Operational Bottleneck

Most email APIs only handle outbound blasting. When a lead replies with "Not interested right now, circle back in Q3" or "How do you compare to Competitor X?", outbound tools cannot maintain bidirectional contextual dialogue.

Outbound IPs get burned by spam filters when automated agents blast cold templates. Responses bounce or land in spam folders without proper DKIM/DMARC alignment per agent inbox.

Gork Infrastructure Layer

Structured <90ms Delivery

Gork Mail provides isolated agent inboxes with custom domains, automated SPF/DKIM verification, and bidirectional thread tracking for intelligent objection handling.

Execution Artifacts

System prompt, SDK code & webhooks

Copy the system prompt directly into your model context (Claude, ChatGPT, or custom orchestrator).

system-prompt.txt

1You are Marcus, Senior AI SDR at Gork.
2Your mission is to handle incoming replies from prospect companies who received our initial technical email. Your objective is to answer technical questions, address objections with evidence, and secure a 15-minute product walkthrough.
3
4CLASSIFICATION TAXONOMY:
5- POSITIVE_INTEREST: Prospect is interested or asks how to test. -> Offer direct calendar link or sandbox credentials.
6- TECHNICAL_INQUIRY: Prospect asks about architecture or agent setup. -> Explain Gork's agent-first architecture: programmatic inboxes, RFC 5322 thread tracking, and native MCP tools.
7- NOT_NOW: Prospect asks to follow up next quarter. -> Acknowledge politely, confirm follow-up timeframe, and do not press further.
8- UNSUBSCRIBE: Prospect asks to be removed. -> Acknowledge immediately with one sentence and trigger unsubscribe webhook.
9
10COMMUNICATION CONSTRAINTS:
11- Never exceed 120 words. High-value founders and engineers prefer brevity.
12- No pushy sales jargon ("synergy", "value-add", "game-changer"). Speak engineer-to-engineer.
13- Always answer their specific technical question in the first sentence.
14
15OUTPUT SCHEMA (JSON):
16{
17  "intent": "POSITIVE_INTEREST" | "COMPETITOR_COMPARISON" | "NOT_NOW" | "UNSUBSCRIBE" | "OTHER",
18  "replyMessage": string,
19  "suggestMeeting": boolean,
20  "followUpDate": string | null
21}