AutoGPT

Use when buyer and seller (or guest and host, traveler and property) both have a case: hear both sides, mediate plainly, and justify any exception.

The English summary is being prepared. Showing the original description.

Use when growing a travel or marketplace partner's revenue through their listing content, rates, promos, and partner-tool reads.

The English summary is being prepared. Showing the original description.

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.

The English summary is being prepared. Showing the original description.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

The English summary is being prepared. Showing the original description.

Analyse lost deals by recorded reason, stage, segment, and age, with gaps in the reasons shown.

The English summary is being prepared. Showing the original description.

Use when goods are moving: trace and expedite shipments, file customs entries, and liaise with carriers and warehouses.

The English summary is being prepared. Showing the original description.

Use when the phones ring, chat piles up, or social mentions burn: work the live queue in order, keep talk tracks short, and move public heat to private.

The English summary is being prepared. Showing the original description.

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

The English summary is being prepared. Showing the original description.

Decide which emails a product should send and what triggers each one, before writing a single subject line.

The English summary is being prepared. Showing the original description.

Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.

The English summary is being prepared. Showing the original description.

Use when a partnership hits its lifecycle tail: change control mid-term, the renewal play from 120 days out, and clean exits with dated transitions.

The English summary is being prepared. Showing the original description.

Compare each ad's promise with its landing page and list the gaps that cost conversions.

The English summary is being prepared. Showing the original description.

Use when a support answer should outlive the case: capture knowledge in the flow of solving, keep help articles findable and right, and coach reuse.

The English summary is being prepared. Showing the original description.

Use when the question is category-level: where the ecosystem plays, where the whitespace is, and whether to build, buy, or partner for each gap.

The English summary is being prepared. Showing the original description.

Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.

The English summary is being prepared. Showing the original description.

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint. For non-leading interview technique, see mom-test.

The English summary is being prepared. Showing the original description.

Use when a job posting needs writing, an old one needs rewriting, or a posting needs a language check before it goes live.

The English summary is being prepared. Showing the original description.

Use on the first conversation with James, or whenever memory has no operations preferences yet: learn the business and its size, the processes that break most, where SOPs and numbers live, who approves spend and process changes, and get to a first real ops deliverable.

The English summary is being prepared. Showing the original description.

Generate a response to a common legal inquiry using configured templates, with built-in escalation checks for situations that shouldn't use a templated reply. Use when responding to data subject requests, litigation hold notices, vendor legal questions, NDA requests from business teams, or subpoenas.

The English summary is being prepared. Showing the original description.

Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches. Use when sizing a market opportunity, estimating addressable market, preparing for investor pitches, or evaluating market entry.

The English summary is being prepared. Showing the original description.

Frame a KPI question with metric definitions, sources, periods, owners, decision use, and data limits before analysis starts.

The English summary is being prepared. Showing the original description.

Plan a launch's messages, channels, owners, timing, and approvals on one page.

The English summary is being prepared. Showing the original description.

Draft a blameless incident review with an evidence-based timeline, causes, and owned follow-ups.

The English summary is being prepared. Showing the original description.

Write lead routing rules that cover every case once, with a fallback and an owner.

The English summary is being prepared. Showing the original description.