# Askpilot > Askpilot is agentic workflow execution infrastructure: AI that runs your business workflows. You connect the tools you already use, describe a workflow to the AI agent your team already uses (Claude, Claude Code, ChatGPT, Codex, Hermes, Gemini or OpenClaw), and Askpilot turns it into a PROCESS.md workflow, starts it on events from your tools, runs it end to end across those tools, pauses for approval when it matters, and keeps every run on record. Built for UK businesses, with estate agencies, IVA providers and phone-led teams as the primary markets. This file describes what is published on askpilot.com, page by page, including what every animated demonstration on the site shows. Every statement below is taken from a live page or from the scripted content that drives its animation. - Website: https://askpilot.com - Pricing: https://askpilot.com/pricing.html - Machine-readable pricing: https://askpilot.com/pricing.md - Remote MCP server: https://mcp.askpilot.com - Support: support@askpilot.com - Sales: sales@askpilot.com - Last updated: 2026-09-07 ## What Askpilot is An AI agent on its own completes individual tasks when prompted or scheduled. It cannot be told the moment something happens in your systems, cannot keep working while nobody is talking to it, and cannot write results back into your tools. Askpilot supplies those things. It holds the connections to your tools, listens for the events that should start work, keeps each run going until it is finished, checks with a person before anything sensitive, and reports back. The agent stays the interface; Askpilot does the running. - Set up from any AI agent. Connect Askpilot once through its remote MCP server (https://mcp.askpilot.com). From then on Claude, ChatGPT, Claude Code, Gemini, Codex and OpenClaw can create, change, pause, hand over, run and delete the same workflows by asking. - Workflows are PROCESS.md files: plain language, with as much structure as you want to add (role, instructions, events, rules, todos, paths). - Triggers: webhook events from connected tools start a new session or continue one that is waiting for exactly that event. Schedules and manual starts also work. - Integrations: CRM, phone system, email, calendar, messaging and any MCP integration. A missing tool is built on request, at no extra cost. - Built-in tools: knowledge search, create and edit documents, Drive and SharePoint sync, web search, deep research. - Approvals: anything sensitive, outside the rules, or needing judgement pauses. The right person gets a desktop pop-up or notification, and every action is recorded. - Full visibility: every run and every action is kept in the runs dashboard. Web app and desktop app are live; mobile is coming soon. - Pricing: pay for the work done, not per seat. Pro from £25 a month for 2,000 credits with unlimited users, 500 free credits to start, Enterprise on request. - Availability: early access. Businesses only. UK first, available globally. ## How the animated demonstrations work Most sections of the home page and the three solution pages contain a looping, scripted mock of a real screen. None of them is a video: every word is in the page source, and small scripts step through the beats, so what is described below is exactly what a visitor sees. The same components repeat across the site: - The Claude window: a chat titled "Claude", the message box "Write a message…", and the footer "Claude is AI and can make mistakes. Please double-check responses." Messages type out, and structured cards (a connector, a PROCESS.md workflow, a report) render inside the reply. - The Askpilot app shell: a sidebar with Ask, Workflows, Sources and Settings, an Open and Done list of sessions, and the user "DK Dom Krpan". Screens inside it: the Workflows register (Name, Trigger, Owner), the Sources list (Name, Access, Updated) and the session view. - The session view: a title bar naming the run (for example "Northgate Ltd · INV-4021"), an "Auto-run on" switch, a feed on the left (the event that started the run, then "Started ", then each action as a line of what it is doing followed by a titled result), a "Process" checklist on the right whose todos tick as the work is done, and an "Ask anything…" box. - Tool screens drawn as those products look: a Stripe invoice, a Street CRM applicant form, the CallSwitch One softphone, a HubSolv case, a Microsoft consent page. Each ends with a "Webhook sent · " pill when the event leaves for Askpilot. Every animation waits until it is on screen, loops when it finishes, and shows a still final state when the visitor prefers reduced motion. ## Home page (https://askpilot.com/) Title: Askpilot: AI That Runs Your Business Workflows Description: Agentic workflow execution infrastructure. Automate lead qualification, customer support or any workflow. Set up and run from Claude, ChatGPT or any AI agent. Header navigation: How it works; Solutions (By use case: Post-call admin; By industry: Estate agents, IVA firms); Integrations; Pricing; Blog; Request early access. ### Hero Heading: "AI that runs your business workflows" Lede: "Qualify leads, chase unpaid invoices, collect documents, or automate any business workflow end to end." Call to action: Request early access. Beneath it: "Works with Claude, Claude Code, ChatGPT, Codex, Hermes, Gemini, OpenClaw." Animated box: the hero run. One macOS-style window whose screen changes through three beats, with a caption on the lid saying what is on screen and where. On load the heading, lede, button and agent list enter in sequence, and the window enters last. 1. Claude (captions: "Connecting Askpilot in Claude", "Askpilot connected in Claude", "Setting up the workflow in Claude", "Workflow live in Askpilot"). - You: "Connect Askpilot. The setup instructions are at askpilot.com/mcp." - Claude: "Askpilot runs and manages long-running business workflows. I will add it as a custom connector." A connector card renders: Askpilot, custom connector. Remote MCP server: https://mcp.askpilot.com. What it does: run and manage long-running business processes. Workspace: Bennett & Co. Then the confirmation "Askpilot connected." - You: "When an invoice goes past due in Stripe, chase the customer until it is paid. Start polite, escalate if there is no reply, and bring me anything that needs a decision." - Claude: "I will set this up in Askpilot as a workflow, so it runs on its own rather than waiting for us to talk again." A PROCESS.md card renders: Invoice chasing. Trigger: An invoice goes past due in Stripe. Todos: Name the run after the invoice; Check what is owed and how late it is; Send the first reminder; Chase until it is paid. Rules: Stop when the invoice is paid or written off; Escalate after five reminders with no reply, to the account owner. - Claude: "That is live now. Askpilot is listening to Stripe, and every overdue invoice gets its own run." 2. Stripe (caption: "An invoice goes unpaid in Stripe"). Invoices › Outstanding › INV-4021. Invoice INV-4021, Past due. Customer Northgate Property Ltd, amount due £2,480.00, billing email accounts@northgate.co.uk, currency GBP, due date 14 August 2026, 17 days overdue, last attempt card declined, reminders sent 0. A pill appears: "Webhook sent · invoice.payment_failed". 3. Askpilot (caption: "Askpilot runs the workflow end to end"). A new session opens and is renamed "Northgate Ltd · INV-4021". Feed: "Invoice past due", then "Started Invoice chasing". Process checklist: Check the invoice and what was already sent; Send the first reminder with a payment link; Follow up until it is paid; Hand it to the account owner. The work, each result ticking a todo: - 09:04 Checking the invoice in Stripe and what we have already sent them. Result "£2,480.00, 17 days overdue": their card was declined on the last attempt and no reminder has gone out yet, so I am starting from the first step. - 09:05 Sending the first reminder, using the approved template. Result "Reminder sent": emailed accounts@northgate.co.uk with the invoice attached and a payment link, and asked for a date if they cannot settle this week. - 09:05 Setting up the follow-ups, so nothing slips if they do not reply. Result "Follow-ups scheduled": I am watching the billing inbox and Stripe for a reply or a payment. If nothing arrives, the next reminder goes out in three working days, up to five in total. - 09:05 Making sure someone picks this up if the reminders do not work. Result "Handover set": if all five reminders go unanswered, this goes to the account owner with everything that has been sent. The loop then starts again from the Claude beat. Under the hero, two credentials: "Official partner" (CallSwitch One) and "Official integration" (iamproperty), each linking to the partner's own announcement. ### Agentic workflow execution Eyebrow "Agentic workflow execution", heading "Fully customisable workflow execution infrastructure." Six tabs; only the selected tab's animation runs. **Askpilot MCP.** "Set up and manage workflows from any AI agent." Connect Askpilot once. Claude, ChatGPT, Claude Code, Gemini, Codex and OpenClaw can then create, change, pause and run the same workflows. Animated box: six agent tiles on the left and the Askpilot Workflows register on the right. Each agent in turn sends one request down a beam into the register, which updates as it lands: - Claude: "Create a workflow that chases missing documents on new tenancies." Result: Created Document chase (a new row, owner Priya, "Created by · Just now"). - ChatGPT: "Pause Invoice chasing over the bank holiday weekend." Result: Paused Invoice chasing. - Claude Code: "Add a rule to Lead qualification: reply within five minutes." Result: Added a rule to Lead qualification. - Gemini: "Hand Customer support over to Priya." Result: Handed Customer support to Priya. - Codex: "Run Post-call admin on this morning's calls now." Result: Ran Post-call admin (the row shows Running). - OpenClaw: "Delete New client onboarding, we no longer use it." Result: Deleted New client onboarding (the row goes). The register lists Document chase, Lead qualification, Invoice chasing, Customer support, Post-call admin and New client onboarding with Name, Access and Updated columns. **Agentic workflow execution.** "Workflows run automatically, from start to finish." Askpilot uses the workflow's instructions, rules, tasks and paths to complete the work across your connected tools. Every run stays visible, with each action recorded. Animated box: first a Street CRM screen (Dashboard › Lettings Applicants › Create). A lettings applicant is created: Sarah Bennett, branch Askpilot, sarah.bennett@gmail.com, +44 7700 900882, budget £1,450 pcm, 2 bedrooms, source website enquiry, move-in 1 September 2026. "Save applicant" is pressed and the toast "Lettings applicant created" appears. The screen crossfades to the Askpilot session "Sarah Bennett · enquiry". Feed: the event "Applicant lettings created" with "Start lead-qualification" (the run was started by the event; the source also carries the alternative of a person asking "Run lead qualification for the new enquiries"). Process: Name the run after the enquiry; Score the lead against the qualification skill; Send the first response; Chase for a reply until they book. Work: 09:12 "Session renamed" (now "Sarah Bennett · enquiry", matching the applicant record in Street); 09:12 "Lead scored 82 / 100" (two bedrooms, £1,450 a month, moving in September; clears the threshold in lead-qualification, so it carries on without asking); 09:13 "Email sent" (to sarah.bennett@gmail.com, offering Thursday 2:00 PM or Friday 11:00 AM and asking the three qualifying questions); 09:13 "Chase scheduled" (listening on her email and WhatsApp; if nothing arrives it follows up tomorrow, then stops once she books). **Integrations.** "Connect the tools your workflows need." Connect your CRM, email, phone, calendar, messaging, or any tools you use. Askpilot uses them across workflows with the permissions you set. Missing one? We build it on request, at no extra cost. Animated box: the Askpilot Sources screen, listing Street CRM (All members, 2 days ago), WhatsApp +44 20 8050 7743 (Only me, 2 days ago) and Calendar (Only me, 4 days ago). A pointer clicks New. The "Add source" panel opens ("Add files, web content, or connect your tools") with Type, Access, Name and Description fields; the placeholder example is a Files source called "HR Policies" ("HR policies, PTO, benefits. Use for employee handbook questions."). The type picker is searched for "out" and Microsoft Outlook is chosen. The panel becomes "Connect Microsoft Outlook: connect your Microsoft account to read and send emails in your Microsoft Outlook", the source is named "Reception inbox" ("Client emails and replies. Use for enquiry follow-ups."), and Connect is pressed. The Microsoft consent page covers the frame (signed in as dom@askpilot.com; "Permissions requested: Askpilot, askpilot.com. This app would like to: sign you in and read your profile, read your mail, send mail as you, maintain access to data you have given it access to"; Cancel or Accept). Accept is pressed, the button runs Connecting… then Connected, and the new row "Reception inbox" (Only me, Just now) appears in the list. **Tools.** "Built-in tools to power your workflows." Every workflow can search your business knowledge, create documents, work with current Drive and SharePoint files, and research the web. All five tools are built into Askpilot and available whenever a workflow needs them. Box: five rows that light up one after another, three seconds each, every row with a workflow example: - Knowledge search: search your indexed business documents for any information a workflow needs to complete its work accurately. Example: answer a tenant's WhatsApp question using the approved wording from your handbook. - Create and edit documents: create new documents or edit existing ones, then return the completed file. Example: create a completed renewal letter using details from the tenancy record. - Drive and SharePoint sync: keep Google Drive and SharePoint files indexed and up to date, so workflows always use the current version. Example: retrieve the latest gas safety certificate from SharePoint before contacting the tenant. - Web search: search the web for current facts and verify details such as company records, listings, addresses and prices. Example: verify that a new supplier is registered before releasing the first payment. - Deep research: investigate larger questions across multiple sources and return a structured answer with links to the evidence. Example: research a corporate landlord and produce a sourced briefing before a pitch. **Triggers.** "Triggers start workflows and keep them moving." Askpilot identifies the exact event each workflow needs, applies the right filter, and subscribes to it. A WhatsApp workflow listens only for replies from that number, then resumes automatically. Animated box: the session "Emma Hughes · enquiry", started by a HubSpot "Form submission created" event. Process: Check the enquiry; Send the qualifying questions; Wait for her reply; Qualify her answers; Offer a viewing time. The run makes tool calls, shown the way an assistant renders them: - outlook.send_email("emma.hughes@outlook.com"), sent: "Hi Emma, a few quick questions so I can find the right places: how many bedrooms, what budget, and when are you looking to move?" - askpilot.list_events("outlook, whatsapp"), 4 results: email.received, email.opened, message.received, message.delivered. It picks email.received and message.received. - A card "Watching for her reply · 2 active": Outlook email.received with the filter from = emma.hughes@outlook.com, and WhatsApp message.received with the filter from = +44 7700 900882. The run waits. - A WhatsApp "Message received" event arrives and resumes the run, which replies with whatsapp.send_message("+44 7700 900882"): "Thanks Emma. I have two viewings free on Thursday at 2:00 PM or Friday at 11:00 AM. Which works better?" **Approvals.** "Approve the sensitive actions you choose." Anything sensitive, outside the rules, or needing judgement pauses. Askpilot sends the right person a desktop pop-up or notification for review or approval, with every action recorded. Animated box: a desktop at 09:41. A notification rises: "Approval needed. Send this WhatsApp to Rachel Adeyemi? 'Hi Rachel, sorry we missed you! Are you free Thursday 2pm or Friday 11am for a viewing?'" with the buttons Edit and "Approve & send". The pointer taps Approve & send and the card confirms "Sent". ### Workflows Eyebrow "Workflows", heading "Automate any business workflow from start to finish." A grid of pre-built workflow cards, each with a department tag, a one-line blurb and its trigger. Clicking a card opens it as the workflow it is (instructions, rules, todos), with the note "Created using the PROCESS.md format. See how PROCESS.md works", linking to the PROCESS.md page. - Lead qualification (Sales): "Reply while the lead is warm, then chase until they are booked in." Trigger: Enquiry created on Street CRM. Instructions: leads from the website are usually price-sensitive, so lead with availability rather than cost; never quote a figure without a manager. Rules: Stop if the lead books an appointment; Escalate after three attempts, tell the branch manager. Todos: Check the lead details (pull the enquiry from Street CRM and score it against the lead-qualification skill); Send the first response (draft from assets/first-response.md, offer availability and ask the qualifying questions); Chase for a reply (follow the lead-follow-up skill and nudge them on WhatsApp); Offer two times (check the diary and offer the next two free slots). - Customer support (Support): "Provide support from your internal FAQ until the case is closed." Trigger: Message received on WhatsApp. Instructions: most questions are already answered in the internal FAQ; look there first and quote it plainly rather than improvising; if the FAQ does not cover it, say so and hand over. Rules: Stop if the customer confirms the case can be closed; Escalate if they ask for a refund or write in twice about the same thing, tell the support lead. - Invoice chasing (Finance): "Chase an overdue invoice politely, then firmly, then hand it over." Trigger: Payment missed on Stripe. Instructions: never threaten and never guess at reasons; use a firmer tone only on the third attempt. Rules: Stop if the invoice is paid; Escalate if it is 30 days or more overdue, tell the account manager. - Post-call admin (Admin): "Turn every call into finished admin before anyone thinks about it." Trigger: Call ended on CallSwitch One. Instructions: log what was agreed, not everything that was said; keep the summary under five lines. Rule: Escalate if the caller raised a complaint, tell the manager the same day. - Missed-call follow-up (Sales): "Text back the moment a call is missed, so nobody quietly slips away." Trigger: Missed call on CallSwitch One. Instructions: speed matters far more than polish here; send within five minutes or it is not worth sending. Rule: Stop if they call back or reply. One todo ("Ask who is calling") requires approval. - Document chase (Admin): "Chase a missing document until it arrives, then file it." Trigger: Document missing on Street CRM. Instructions: most people forget rather than refuse, so keep the first two chases friendly; only firm up on the third. Rules: Stop if the document arrives; Escalate after three attempts, tell the case owner. - New client onboarding (Ops): "Take a signed client from contract through to fully set up." Trigger: Start session manually. Instructions: the first week sets the tone; confirm everything in writing, even where a call has already happened. Rule: Escalate if anything is still missing after five working days. - Create your own (Custom): "Create a completely custom workflow." ### Triggers Eyebrow "Triggers", heading "Whatever happens in your tools can trigger Askpilot." Animated box in three columns: on the left, tools sending real events; in the middle, the trigger showing the event, the filter and what it does; on the right, "Sessions in Askpilot" (Open), where an event either starts a new session or wakes one that was waiting for exactly that. Six beats, each with its own caption: 1. "An invoice fails in Stripe": Stripe invoice.payment_failed, INV-4021 · £2,480 past due → Workflow Invoice chasing, starts a new session → "Invoice chasing starts". 2. "Sarah replies on WhatsApp": WhatsApp inbound.message, +44 7700 900882 · "Great, can I view it on Thursday?" → Session Customer support · Sarah Bennett, continues the waiting session → "Customer support continues". 3. "A lettings enquiry lands in Street CRM": Street CRM enquiry.created, Tom Iqbal · 2 bed, Guildford → Workflow Lead qualification, starts a new session → "Lead qualification starts". 4. "A message from an unknown number": WhatsApp inbound.message, +44 7700 123456 · "Do you do valuations?" → Filter from = +44 7700 900882, no match, nothing starts → "Nothing is listening. Ignored". 5. "Northgate replies by email": Outlook email.received, accounts@northgate.co.uk · Re: Invoice INV-4021 → Session Invoice chasing · Northgate Ltd, continues the waiting session → "Invoice chasing continues". 6. "A call ends in CallSwitch One": CallSwitch One call.ended, 07700 900123 · 4 min 12 s → Workflow Post-call admin, starts a new session → "Post-call admin starts". The sessions list holds Post-call admin (07700 900123), Lead qualification (Tom Iqbal), Invoice chasing (Northgate Ltd), Customer support (Sarah Bennett) and Document chase (12 Elm Road). Each row moves between Started, Waiting for a reply (or Waiting for a file) and Resumed as the beats play. ### Every company process, documented Heading "Every company process, documented", lede "Build the system of record for how your company works." Animated box: one window, two screens. First a person and Claude work out a workflow together; then the same window shows the Askpilot Workflows register it now lives in, with the new row arriving. - You: "We keep losing leads because nobody gets back to them fast enough. Can you set something up in Askpilot so every new enquiry gets a proper follow-up?" - Claude: "Yes. Two quick questions so I get it right: where do new enquiries land, and what should happen to each one?" - You: "They come into Street CRM. Reply straight away and ask the usual things: budget, when they want to move, who is moving in, whether they are working, and pets. Then keep chasing until they book a viewing. If they go quiet, try WhatsApp as well." - Claude: "Got it. Here is the process. It starts the moment an enquiry is created in Street CRM, qualifies them on the things you named, and stops once a viewing is booked." Card: Lead qualification. Trigger: Enquiry created in Street CRM. Process: Reply to the enquiry within minutes; Ask budget, move-in date, who is moving in, employment and pets; Check affordability and right to rent before offering a viewing; Chase by email, then WhatsApp; Book the viewing once they qualify. Sources: Street CRM, Outlook, WhatsApp. Rules: Stop when a viewing is booked; Escalate after three chases with no reply, to Sarah. - You: "That is exactly it. Make it live in Askpilot." - Claude: "Done. Lead qualification is now in Askpilot, owned by Sarah. It will start every time a new enquiry is created in Street CRM." The register (Name, Trigger, Owner): Lead qualification (Sales; Street CRM · Enquiry created; Sarah M.; the row that arrives), Customer support (Support; WhatsApp · Message received; Priya A.), Invoice chasing (Finance; Stripe · Payment missed; Dom K.), Post-call admin (Admin; CallSwitch One · Call ended; Tom I.), Missed-call follow-up (Sales; CallSwitch One · Missed call; Sarah M.), Document chase (Admin; Street CRM · Document missing; James O.), New client onboarding (Ops; Manual · Started by hand; Dom K.). ### How it works Eyebrow "How it works", heading "Get your first workflow running in minutes." Five steps, each with its own animated window. - Step 01, "Activate your Askpilot account." Sign up and start your free trial. You get 500 free credits to run your first workflows. Box: a sign-up form (first name, last name, email, Continue; or Continue with Google, Continue with Microsoft; "By creating an account, you agree to the Terms of Service and Privacy Policy"), then a Stripe checkout ("Try Askpilot. Free trial for 14 days. Total due today £0.00. Payment details. Start trial. You will not be charged today. We will remind you before the trial ends."), then "Account created: your workspace is ready and the 14-day trial has started. Workspace Bennett & Co. Plan Askpilot Pro · trial. Trial ends in 14 days", then the button "Open in Claude" (with "Open in another platform" and "Continue to Askpilot"). - Step 02, "Install Askpilot MCP in any AI agent." Works with Claude, Claude Code, ChatGPT, Codex, Hermes, Gemini, OpenClaw. Box: the Claude window. You: "Connect Askpilot. The setup instructions are at askpilot.com/mcp." Claude: "Askpilot runs and manages long-running business workflows. I will add it as a custom connector." The connector card (Askpilot, custom connector, remote MCP server https://mcp.askpilot.com, workspace Bennett & Co), then an Askpilot sign-in window ("Sign in to continue. Claude is asking to connect to your workspace."), then consent ("Allow Claude to use Askpilot?"), then "Askpilot connected". - Step 03, "Set up a workflow from your AI agent." Create new and manage workflows by talking to your AI agent. Box: You: "When an invoice becomes overdue in Stripe, chase the business by email until it is paid. Send up to five reminders in the business tone you already know, and escalate to the account owner if it is still unpaid." Claude: "Here it is. It starts on the Stripe event and stops as soon as the invoice is paid. Have a look, and approve it if it reads right." A PROCESS.md card: Invoice chasing. Trigger: Invoice becomes overdue in Stripe. Todos: Check the invoice and what was already sent; Send the first reminder with a payment link; Follow up until it is paid; Hand it to the account owner. Sources: Stripe, Outlook. Rules: Stop when the invoice is paid in Stripe; Escalate after five reminders, to the account owner. The person approves it, and Claude: "Askpilot is watching Stripe for unpaid invoices. Every time one goes overdue, it runs the Invoice chasing workflow." - Step 04, "Workflow runs automatically in Askpilot." Askpilot runs the workflows set up by your AI agent end to end. Box: the same Stripe invoice screen and the same "Northgate Ltd · INV-4021" session as the hero, played from the event on (hero beats 2 and 3). - Reports, "Get daily reports or ask for any." Askpilot reports on your workflows every morning, or whenever you ask. Box: You: "Provide report about executed workflows." Claude: "Here is everything Askpilot ran yesterday." A report card: Lead qualification 18 runs · 12 booked; Invoice chasing 11 runs · £8,400 collected; Document collection 6 runs · all complete; Missed-call follow-up 3 runs · 2 called back. Then "One run needs you: Priya Anand asked to split her invoice. Everything else finished on its own." The window then shows Claude's Scheduled tasks screen, where the same report is set to run every morning (the "Daily briefing" template: "What needs your attention today across calendar, email, and messages", weekdays at 8:00 AM). Call to action: Request early access. ### Full visibility Heading "See every run and action, from open to done." Box: the runs dashboard (Open and Done tabs) with the rows Viewing rebook · Rachel Adeyemi (Missed-call follow-up, "Needs your approval", pulsing because it is waiting on a person), Compliance chase · 42 Oakfield Rd (EPC & gas safety reminder, Running), Call logged → Street CRM (Inbound call · transcript attached, Done · 2m ago) and Offer recap email · Priya Anand (Post-call follow-up, Done · 14m ago). While on screen the running row finishes (spinner to tick, "Running" to "Done · just now", header stat "3 running · 1 needs you"), holds, then resets and loops. Apps: Web app (live), Desktop app (live), Mobile (coming soon). ### Our ecosystem Heading "Built alongside the businesses shaping modern work." - Official partner: CallSwitch One, the cloud phone system from Nebula, used by more than 200,000 business users across the UK. Announcement: "CallSwitch One partners with Askpilot to save users hours on admin after every call" (callswitchone.com). - Official integration: iamproperty, the CRM used by more than 7,000 estate agency branches across the UK. Announcement: "Askpilot Integration for iamproperty CRM" (iamproperty.com). - Quote from James Hay, Director, The Home Club (Best Lettings Agency, Surrey, UK Property Awards, winner four years running; 4.9 with 180+ Google reviews): "You didn't turn up to automate an estate agency, you turned up to understand one first. That's why this actually looks like what agents need, not what a tech company thinks they need. AI should take the jobs nobody wants to do. The chasing, the re-keying, the same admin over and over. What it doesn't touch is the human side. A nervous landlord, a tricky application, a judgement call. That's still us, and we have more time in the day to do more for our clients." ### Pricing (on the home page) Eyebrow "Pricing", heading "Pay only for the work done. Not per seat." A GBP / USD switch, the Pro and Enterprise cards, the credit estimates, the free trial and expert setup notes, and the link "Are you an AI agent? See pricing" to https://askpilot.com/pricing.md. The content is identical to the pricing page (see Pricing below). ### Closing "Ready to take repetitive work off your team's plate?" "Connect Askpilot to your AI agent and start running workflows." Request early access. Footer: Product (How it works, Pricing, PROCESS.md, Security); Solutions (Post-call admin, Estate agents, IVA firms); Integrations (All integrations, CallSwitch One, iamproperty, Street CRM); Company (Request early access, Blog, Brand, Contact, Legal, DPA). ## Post-call admin (https://askpilot.com/use-cases/post-call-admin.html) Title: Automate Post-Call Admin with AI | Askpilot Description: Update the CRM, send follow-ups, create tasks or any workflow you need after a call ends. Set up post-call automation from Claude, ChatGPT or any AI agent. The page has the same structure as the home page (hero run, capability tabs, Workflows grid, register, How it works, Full visibility, pricing, closing), with every scenario written in post-call terms and the CallSwitch One phone system as the tool where the event happens. Two sections are this page's own: "Beyond transcripts" and "Why Askpilot". ### Hero Heading "Automate post-call admin with AI". Lede: "Transcribe calls, update your CRM, send follow-ups, create tasks, or automate any post-call workflow end to end." Request early access. Works with the same seven agents. Animated box, three beats: 1. Claude: the connection (identical to the home page), then You: "When a call ends in CallSwitch One, match it to the right record, log what was agreed, send the follow-up we promised on the call, and raise any task the caller asked for. If a request has no clear owner, bring it to me." Claude: "Here it is. It starts the moment a call ends and stops once the admin is done. Have a look, and approve it if it reads right." Card: Post-call admin. Trigger: A call ends in CallSwitch One. Todos: Match the call to the right record; Log the summary and the key details; Send the follow-up we promised; Raise any task the caller asked for. Sources: CallSwitch One, Street CRM, Outlook. Rules: Stop when the call is logged and the follow-up is sent; Escalate if the caller asked for something no one owns. Claude: "Active. Askpilot is listening to the phone system now, and every call gets its own run." 2. CallSwitch One (caption "A call ends in CallSwitch One"): the softphone as it is at callswitchone.app, with its red rail. Contacts show the caller ID +44 20 3051 4687, the Default Hunt Group and the extensions 1001 Priya A., 1002 Tom I. and 1003 Dom K. Priya opens the keypad and dials +447700900614. The in-call screen shows Sarah Mitchell, +44 7700 900614, with the timer running to 04:12, then she hangs up. The History tab (Missed Calls, Parked, Voicemail) lists today's calls, and "Sarah Mitchell · Outbound · Ext 1001 · Priya A. · Ended 4m 12s · 14:32" arrives at the top above Daniel Okafor (Outbound · Ext 1001, 7m 38s, 11:05), +44 7911 123 456 (Missed · Main line, 10:41) and Rachel Adeyemi (Inbound · Main line · answered by Tom I., 2m 04s, 09:18). Pill: "Webhook sent · call.ended". 3. Askpilot (caption "Askpilot runs the workflow end to end"): session "Sarah Mitchell · 14:32". Feed: "Call ended", then "Started Post-call admin". Process: Match the call to the right record; Log the summary and the key details; Send the follow-up we promised; Raise any task the caller asked for. Work: Matching the number to a record in Street CRM, result "Call matched": Sarah Mitchell, called back by Priya from Ext 1001, 4m 12s. Writing up what was asked and what was agreed, result "Summary logged": she asked to view 14 Foxley Mews on Thursday afternoon; logged on her record with the recording attached. Sending the follow-up Priya promised on the call, result "Follow-up sent": emailed sarah.mitchell@gmail.com with the Thursday slot, directions and Priya as the contact. Raising the task the caller asked for, result "Task created": property pack for 14 Foxley Mews, assigned to Priya, due Thursday 09:00. ### Agentic workflow execution (tabs) The same six tabs and copy as the home page. Three panels carry this page's own scenario: - Agentic workflow execution: the CallSwitch One screen, then the session "Sarah Mitchell · call", started by "Call ended" with "Start post-call-admin" (the source also carries "Run post-call admin for this afternoon's calls" as the asked-for alternative). Work: "Call matched" (Sarah Mitchell, outbound from Ext 1001 by Priya, 4m 12s); "Summary logged" (asked to view 14 Foxley Mews on Thursday afternoon); "Follow-up sent" (confirmation email with the Thursday slot and directions); "Task created" (assigned to Priya, due Thursday 09:00). - Integrations: the Sources list holds Street CRM (All members), Reception inbox (Outlook, Only me) and Calendar. The pointer searches "call" and adds CallSwitch One ("Connect your CallSwitch One account to read and transcribe calls and voicemails"), named "Main line" ("Calls on the main line. Use for post-call admin and follow-ups."), which appears as a new row with access All members. - Triggers: the session "Sarah Mitchell · call", started by a CallSwitch One "Call ended" event. Process: Check the call; Send the follow-up; Wait for her reply; Read her reply; Book the callback. Calls: outlook.send_email("sarah.mitchell@gmail.com"), "Hi Sarah, confirming what we discussed on the call: a viewing at 14 Foxley Mews on Thursday…"; askpilot.list_events("outlook, callswitch one"); a watch card for Outlook email.received (from = sarah.mitchell@gmail.com) and CallSwitch One call.ended (from = +44 7700 900614). An Outlook "Email received" event resumes the run, which replies by email: "Thursday at 2:00 PM is booked. It is in the diary and Priya will meet you there." ### Workflows Heading "Automate any post-call workflow from start to finish." Pre-built post-call workflows: - Call logged (After the call): "Every answered call written up on the right record, with no typing." Trigger: Call ended on CallSwitch One. - Follow-up sent (After the call): "The email you promised on the call, sent while it is still fresh." Trigger: Call ended on CallSwitch One. - Task created (After the call): "Whatever the caller asked for, raised on the right person with a date." Trigger: Call ended on CallSwitch One. - Missed call chased (No answer): "Nobody picked up, so Askpilot texts them back within minutes." Trigger: Missed call on CallSwitch One. - Callback booked (No decision): "The call ended with no decision, so Askpilot books the next one." Trigger: Call ended on CallSwitch One. - Daily call report (Every day): "One message each morning: what came in, and what still needs a person." Trigger: Every weekday at 08:00. - Voicemail handled (No answer): "Every voicemail transcribed, logged and answered the same hour." Trigger: Voicemail left on CallSwitch One. - Create your own (Custom): "Create a completely custom workflow." ### Every company process, documented The same section as the home page, with this page's conversation and rows. - You: "We miss calls all day and nobody rings people back. Can you set something up in Askpilot so every missed call gets chased?" - Claude: "Yes. Two quick questions so I get it right: which phone system do the calls come through, and what should happen when one is missed?" - You: "CallSwitch One. Text them back straight away with a callback window, log it on their record in Street CRM, and if they are already a customer tell whoever owns them. Try once more the next morning, then stop." - Claude: "Got it. Here is the process. It starts the moment a call is missed in CallSwitch One, replies within minutes, and stops once they call back or reply." Card: Missed call chased. Trigger: Missed call in CallSwitch One. Process: Match the number to a record in Street CRM; Text back within minutes with a callback window; Log the missed call and the reply on their record; Route existing customers to whoever owns them; Chase once more the next morning, then stop. Sources: CallSwitch One, Street CRM, WhatsApp. Rules: Stop when they call back or reply; Escalate after two attempts with no reply, to the team lead. - You: "That is exactly it. Make it live in Askpilot." - Claude: "Done. Missed call chased is now in Askpilot, owned by Priya. It will start every time a call is missed in CallSwitch One." Register rows: Missed call chased (Reception; CallSwitch One · Missed call; Priya A.; the row that arrives), Call logged (Admin; Call ended; Tom I.), Follow-up sent (Sales; Call ended; Priya A.), Task created (Admin; Call ended; Dom K.), Callback booked (Sales; Call ended; Priya A.), Voicemail handled (Reception; Voicemail left; Tom I.), Daily call report (Ops; Schedule · Every weekday at 08:00; Dom K.). ### How it works The same five steps as the home page. Step 03 shows the post-call admin conversation from the hero; step 04 shows the CallSwitch One screen and the "Sarah Mitchell · 14:32" session. Reports: "Here is everything Askpilot ran after yesterday's calls." Call logged 64 runs · all logged; Follow-up sent 31 runs · 29 sent same hour; Task created 18 runs · 18 assigned; Missed call chased 9 runs · 6 called back. "One run needs you: a caller asked for a discount on renewal. Everything else finished on its own." ### Beyond transcripts Eyebrow "What it does", heading "Beyond transcripts. Every call, intelligently logged." - Intelligent data logging: "Key details extracted and logged." Askpilot analyses every call, extracts key details like names and budgets, then logs them in the right CRM record or any tool. Animated box: a live call transcript (unknown caller, inbound +44 7700 900882) types out on the left. Askpilot is "Listening to the call"; as it recognises each detail it draws a connector to the iamproperty CRM on the right (Properties › New listing, To let), which fills field by field (property address, monthly rent, furnishing, available from, management, source "Inbound call · logged by Askpilot"), then the full transcript attaches as a PDF. A second screen shows the letting compliance checklist Askpilot builds for the new instruction (42 Oakfield Road › Compliance, "Recognised: new letting"): EPC, Gas safety (CP12), Right to Rent check, Deposit protection, EICR (electrical). Items the call covered tick green; the rest are flagged outstanding, tracked but not actioned. - Uncertain data logging: "No duplicates. No wrong matches." When matching is uncertain or required details are missing, Askpilot asks for clarification before creating or updating a record. Animated box: a live call with no CRM record found for +44 7700 900882. The desktop shows the call pill ("You're on a call with +44 7700 900882"), which expands into an Askpilot question: "New caller, your input needed. No record matched +44 7700 900882. I caught their details on the call, review and create the contact?" with Name Emma Hughes, Phone +44 7700 900882, Email emma.hughes@gmail.com, Type New applicant, and the buttons Skip and Create contact. Create contact is pressed and the card shows "Created". ### Why Askpilot Heading "Your team manages the calls. Askpilot manages the admin." - On the call, written up automatically: "Focus on the call, not taking notes." No scribbled notes or half-listening while you type. Talk to the caller while Askpilot writes everything up for you in the background. Nothing forgotten. - Mobile, waiting back at the office: "Calls logged, even while you're talking on the go." Taking a call on your mobile and away from your desk? Askpilot still intelligently logs the call data and gets the post-call admin done in the background. - "Every call transcript, in one searchable place." No chasing colleagues or relistening to calls. Every conversation is transcribed and kept in one place. Search it, or just ask, and get the answer in seconds. The card shows Sarah Mitchell, Tue · 4m 12s: "…asked to view 14 Foxley Mews on Thursday afternoon." ### Full visibility and partnership The same runs dashboard as the home page, with the first row "Callback booked · Rachel Adeyemi" (Missed-call follow-up, Needs your approval). "Askpilot is now an official CallSwitch One partner." Linked announcement: "CallSwitch One partners with Askpilot to save users hours on admin after every call" (callswitchone.com). Then pricing and the closing call to action, as on the home page. ## Estate agents (https://askpilot.com/industries/estate-agents/) Title: Automate Estate Agency Workflows with AI | Askpilot Description: Answer enquiries, book viewings, chase certificates or any workflow your agency needs. Set up agency workflow automation from Claude, ChatGPT or any AI agent. The same structure as the home page, written for UK estate and letting agencies with Street CRM as the tool where the event happens. ### Hero Heading "Automate your estate agency workflows with AI". Lede: "Answer portal enquiries, book viewings, chase certificates, or automate any business workflow end to end." Request early access. Works with the same seven agents. Animated box, three beats: 1. Claude: the connection, then You: "When a new enquiry comes into Street CRM, match it to the property, reply within minutes with two viewing slots and the qualifying questions, chase by email then WhatsApp if they go quiet, and book the viewing once they qualify. Bring me anything that needs a decision." Claude: "Here it is. It starts on the enquiry and stops as soon as the viewing is booked. Have a look, and approve it if it reads right." Card: Enquiry to viewing. Trigger: Enquiry created in Street CRM. Todos: Match the enquiry to the right property; Send the first response with availability; Chase by email, then WhatsApp; Book the viewing and confirm it. Sources: Street CRM, Outlook, WhatsApp. Rules: Stop when the viewing is booked; Escalate after three attempts with no reply, to the branch manager. Claude: "Active. Askpilot is watching Street CRM for new enquiries now, and every one gets its own run." 2. Street CRM (caption "An enquiry lands in Street CRM"): the Create Lettings Applicant form for Sarah Bennett (branch Askpilot, sarah.bennett@gmail.com, +44 7700 900882, budget £1,450 pcm, 2 bedrooms, source website enquiry, move-in 1 September 2026). Save applicant is pressed, the form shows "Saved", and the pill "Webhook sent · applicant.created" appears. 3. Askpilot: session "Sarah Bennett · enquiry". Feed: "Enquiry created", then "Started Enquiry to viewing". Process: the four todos above. Work: Checking the enquiry and the property it came from, result "Enquiry matched": two-bed flat on Northgate Road, asked about availability and a September move. Sending the first response with two viewing slots and the qualifying questions, result "First response sent": emailed sarah.bennett@gmail.com offering Thursday 5:30pm or Saturday 10am, and asked about budget, move-in date and who is moving in. Setting up the chase, so nothing slips if she goes quiet, result "Chase scheduled": watching her email and WhatsApp for a reply; if nothing arrives by tomorrow morning the nudge goes out on WhatsApp, up to three in total. Holding the viewing slots so they can be confirmed the moment she picks one, result "Slots held": Thursday 5:30pm and Saturday 10am are held in the diary; whichever she picks is confirmed to her and logged in Street. ### Agentic workflow execution (tabs) The same six tabs. The run tab shows the Street CRM applicant screen and the "Sarah Bennett · enquiry" session, started by "Applicant lettings created" with "Start enquiry-to-viewing" ("Run enquiry to viewing for this morning's portal enquiries" is the asked-for alternative), with the four results above. The Integrations tab is the home page's Outlook flow. The Triggers tab: the session "Sarah Bennett · enquiry", started by a Street CRM "Enquiry created" event. Process: Check the enquiry; Send the first response; Wait for her reply; Read her reply; Book the viewing. It emails sarah.bennett@gmail.com ("Hi Sarah, thanks for your enquiry about Northgate Road. I can offer a viewing on…"), lists the events Outlook and WhatsApp publish, watches email.received (from = sarah.bennett@gmail.com) and message.received (from = +44 7700 900882), and when her WhatsApp "Message received" arrives replies "Thursday at 5:30 PM is booked. It is in the diary and Priya will meet you there." ### Workflows Heading "Automate any agency workflow from start to finish." Pre-built agency workflows: - Enquiry to viewing (Sales): "Answer a portal enquiry fast and chase until the viewing is booked." Trigger: Enquiry received on Rightmove. - Viewing feedback (Sales): "Collect feedback after a viewing and send it to the vendor same day." Trigger: Viewing completed on Street CRM. - Sales progression (Sales): "Keep a sale moving from offer to exchange, chasing whoever goes quiet." Trigger: Offer accepted on Street CRM. - Compliance chase (Lettings): "Chase an expiring certificate until the new one is on file." Trigger: Certificate expiring on Street CRM. - Tenancy setup (Lettings): "Take an accepted application through referencing to a signed tenancy." Trigger: Application accepted on Street CRM. - Missed-call follow-up (Sales): "Text back the moment a call is missed, so nobody rings elsewhere." Trigger: Missed call on CallSwitch One. - Valuation follow-up (Sales): "Send the appraisal the same day and chase until the vendor instructs or says no." Trigger: Valuation booked on Street CRM. - Create your own (Custom): "Create a completely custom workflow." ### Every company process, documented - You: "Vendors keep ringing us for feedback after viewings and we never get to it. Can you set something up in Askpilot so every viewing gets feedback back to the vendor the same day?" - Claude: "Yes. Two quick questions so I get it right: where are viewings recorded, and what should happen once one finishes?" - You: "They are in Street CRM. Message the applicant within an hour, ask what they thought and whether they want a second look, then write it up for the vendor and log it on the property. If they sound keen, tell the negotiator." - Claude: "Got it. Here is the process. It starts the moment a viewing is marked completed in Street CRM, asks while it is fresh, and stops once the vendor has the feedback." Card: Viewing feedback. Trigger: Viewing completed in Street CRM. Process: Message the applicant within an hour of the viewing; Ask what they thought and whether they want a second look; Chase once by WhatsApp if there is no reply; Write it up for the vendor and send it the same day; Log it against the property and flag keen applicants to the negotiator. Sources: Street CRM, Outlook, WhatsApp. Rules: Stop when the vendor has the feedback; Escalate if the applicant sounds like an offer, to the negotiator. - You: "That is exactly it. Make it live in Askpilot." - Claude: "Done. Viewing feedback is now in Askpilot, owned by Priya. It will start every time a viewing is completed in Street CRM." Register rows: Viewing feedback (Sales; Street CRM · Viewing completed; Priya A.; the row that arrives), Enquiry to viewing (Sales; Enquiry created; Sarah M.), Sales progression (Sales; Offer accepted; Tom I.), Compliance chase (Lettings; Certificate expiring; James O.), Tenancy setup (Lettings; Application accepted; Dom K.), Missed-call follow-up (Sales; CallSwitch One · Missed call; Sarah M.), Valuation follow-up (Sales; Valuation booked; Tom I.). ### How it works The same five steps. Step 03 shows the enquiry-to-viewing conversation; step 04 shows the Street CRM screen and the "Sarah Bennett · enquiry" session. Reports: "Here is everything Askpilot ran across the branch yesterday." Enquiry to viewing 18 runs · 12 booked; Viewing feedback 11 runs · all sent same day; Compliance chase 6 runs · 4 certificates filed; Sales progression 3 runs · 2 chased. "One run needs you: a vendor asked to reduce the asking price. Everything else finished on its own." ### Full visibility, ecosystem, pricing, closing The runs dashboard as on the home page. "Our ecosystem: Developed with estate agents, for estate agents." with the CallSwitch One partner card, the iamproperty integration card and the James Hay quote. Then pricing and the closing call to action. ## IVA providers (https://askpilot.com/industries/iva-providers/) Title: Automate IVA Workflows with AI | Askpilot Description: Annual reviews, missed payments, income evidence or any workflow your practice needs. Set up IVA workflow automation from Claude, ChatGPT or any AI agent. The same structure, written for insolvency practices running Individual Voluntary Arrangements, with the HubSolv (Aryza) case management system as the tool where the event happens. ### Hero Heading "Automate your IVA workflows with AI". Lede: "Run annual reviews, chase missed payments, collect income evidence, or automate any business workflow end to end." Request early access. Works with the same seven agents. Animated box, three beats: 1. Claude: the connection, then You: "When a payment fails on a case in HubSolv, confirm the arrears, send the notice of breach, chase by email then SMS until the client responds, and refer it to the supervisor after three missed payments. Ask me before anything goes to creditors." Claude: "Here it is. It starts on the failed payment and stops as soon as the arrears are cleared. Have a look, and approve it if it reads right." Card: Missed payment. Trigger: Payment failed in HubSolv. Todos: Confirm the missed payment and the amount; Send the notice of breach; Chase until the client responds; Refer it to the supervisor. Sources: HubSolv, Outlook, SMS. Rules: Stop when the arrears are cleared or a catch-up is agreed; Escalate after three missed payments, to the supervisor. Claude: "Active. Askpilot is watching HubSolv for failed payments now, and every one gets its own run." 2. HubSolv (caption "A payment fails in HubSolv"): Cases › Active › CASE-4482, Payment failed. Client Daniel Whitfield, monthly contribution £180.00, email d.whitfield@northgate.co.uk, supervisor Priya Anand; contributions due 1 September 2026, missed payments 2, arrears £360.00, last contact 14 days ago. Pill: "Webhook sent · payment.failed". 3. Askpilot: session "D. Whitfield · CASE-4482". Feed: "Payment failed", then "Started Missed payment". Process: the four todos above. Work: Checking the case in HubSolv and what was already sent, result "Case checked": two payments missed, £360 in arrears; last contact was 14 days ago, and no notice has gone out yet. Sending the notice of breach, using the approved template, result "Notice sent": emailed d.whitfield@northgate.co.uk and sent by SMS; it sets out the arrears, gives 30 days to respond, and asks how it will be put right. Setting up the chase, so nothing slips if he does not reply, result "Chase scheduled": watching his email and SMS for a reply or a payment; if nothing arrives in seven days the next chase goes out, up to three in total. Making sure the supervisor picks this up if the chases do not work, result "Referral set": after three missed payments, or three chases with no reply, this goes to Priya with everything that has been sent. ### Agentic workflow execution (tabs) The run tab opens on the same Street CRM applicant screen as the home page, then crossfades to the HubSolv session "D. Whitfield · CASE-4482", started by "Payment failed" with "Start missed-payment" ("Run missed payment for every case in arrears this morning" is the asked-for alternative). The Triggers tab: the session "D. Whitfield · CASE-4482", started by a HubSolv "Payment failed" event. Process: Check the case; Send the notice of breach; Wait for his reply; Read his reply; Record what was agreed. It emails d.whitfield@northgate.co.uk ("Dear Mr Whitfield, two contributions to your arrangement have been missed and the arrears…"), lists the events Outlook and HubSolv publish, watches email.received (from = d.whitfield@northgate.co.uk) and sms.received (from = +44 7700 900412), and when his "Email received" arrives replies "Thank you. A catch-up of £60 on top of the usual £180 for the next six months is agreed…". ### Workflows Heading "Automate any IVA workflow from start to finish." Pre-built IVA workflows: - Annual review (Casework): "Collect income evidence and put the review to the supervisor." Trigger: Review due. - Missed payment (Compliance): "Issue the breach notice, agree how it is put right, record it." Trigger: Payment failed on HubSolv. - Evidence chase (Admin): "Chase a missing payslip or statement, then file it against the case." Trigger: Document missing on HubSolv. - Client take-on (Onboarding): "Take a signed proposal through to a case that is properly set up." Trigger: Proposal signed on HubSolv. - Creditor queries (Correspondence): "Answer routine creditor post and route anything contentious onward." Trigger: Creditor email on Outlook. - Variation proposal (Casework): "Prepare a variation and put it to the practitioner before creditors." Trigger: Circumstances changed on HubSolv. - Case closure (Casework): "Take the final payment through to a certificate of completion and a closed case." Trigger: Final payment received on HubSolv. - Create your own (Custom): "Create a completely custom workflow." ### Every company process, documented - You: "Annual reviews pile up and we end up chasing income evidence for weeks. Can you set something up in Askpilot so every review gets its evidence in on time?" - Claude: "Yes. Two quick questions so I get it right: where does the review date live, and what do you need from the client?" - You: "The anniversary date is on the case in HubSolv. Sixty days out, ask for payslips, the latest P60 and three months of bank statements. Chase by email then SMS, and once everything is in, put the review to the supervisor." - Claude: "Got it. Here is the process. It starts sixty days before the anniversary, asks once clearly with a deadline, and stops once the review is filed." Card: Annual review. Trigger: Review due, 60 days before the anniversary in HubSolv. Process: Check what the file already holds and list what is missing; Request payslips, the latest P60 and three months of bank statements; Chase by email, then SMS, until it all arrives; Rebuild the income and expenditure from the evidence; Put the review to the supervisor. Sources: HubSolv, Outlook, SMS. Rules: Stop when the review is filed; Escalate if nothing arrives after three attempts, to the supervisor. - You: "That is exactly it. Make it live in Askpilot." - Claude: "Done. Annual review is now in Askpilot, owned by Priya. It will start sixty days before every anniversary date in HubSolv." Register rows: Annual review (Casework; HubSolv · Review due; Priya A.; the row that arrives), Missed payment (Compliance; Payment failed; Dom K.), Evidence chase (Admin; Document missing; Tom I.), Client take-on (Onboarding; Proposal signed; Sarah M.), Creditor queries (Correspondence; Outlook · Creditor email; James O.), Variation proposal (Casework; Circumstances changed; Dom K.), Case closure (Casework; Final payment received; Sarah M.). ### How it works The same five steps. Step 03 shows the missed-payment conversation; step 04 shows the HubSolv screen and the "D. Whitfield · CASE-4482" session. Reports: "Here is everything Askpilot ran across the caseload yesterday." Annual review 18 cases · 12 filed; Missed payment 11 cases · 7 back on track; Evidence chase 6 cases · all received; Creditor queries 3 cases · 2 answered. "One case needs you: Priya Anand asked to reduce her payment. Everything else finished on its own." ### Controlled automation Eyebrow "Controlled automation", heading "Automate the processes. Keep judgement human." Three animated cards: - "Routine casework keeps moving." Askpilot carries out information requests, reminders, document checks and record updates across your connected systems. Card: Request client documents (Email); Update the case record (Case platform); Prepare adviser handover (Review pack), each ticking in turn. - "Your rules control the process." Define approval points, stop conditions and who handles each exception. Askpilot follows those rules and records every action. Card: IVA process controls: Steps defined, Approvals set, Exceptions routed; "Controls active". - "Judgement stays with authorised people." When an action requires advice or judgement, Askpilot pauses and routes it to the right adviser or insolvency practitioner. Card: "Human review needed: the client reported a change in circumstances." Review or Route; "Routed. Handed to an adviser." This section sits after the runs dashboard ("Full visibility", as on the home page) and before pricing and the closing call to action. ## Integrations (https://askpilot.com/integrations.html) Title: Integrations: Any Tool Your Workflows Need | Askpilot Description: Connect any tool your workflows need to run. Missing one? Askpilot builds it on request, at no extra cost. Heading "Connect the business tools you already use." Lede: "Connect any tool your workflows need to run. Missing one? Askpilot builds it on request, at no extra cost." Calls to action: Request early access, Call us. A pulsing pill: "New integrations ship every month". Works with Claude, Claude Code, ChatGPT, Codex, Hermes, Gemini, OpenClaw. Featured integrations, each with a "View integration" link: - CallSwitch One (phone system): a cloud phone system from Nebula, used by 200,000+ UK business users. - iamproperty (CRM platform): a cloud CRM for UK estate agents, used by 7,000+ branches. - Street CRM (CRM platform): a cloud CRM for UK estate and letting agents, all in one system. Also listed: Microsoft Outlook, Outlook Calendar, Google Calendar, Google Drive, Gmail, WhatsApp, SharePoint, Trello, Yay.com, and any MCP integration. Closing: "Ready to take repetitive work off your team's plate? Connect Askpilot to your AI agent and start running workflows." Request early access, Call us. ## Askpilot + Street CRM (https://askpilot.com/integrations/street.html) Title: Automate Street CRM Workflows with AI | Askpilot Description: Start workflows on Street CRM events: a new enquiry, a booked viewing, an accepted offer. Set up Street CRM automation from Claude, ChatGPT or any AI agent. An integration profile page. Heading "Run your Street CRM workflows from Claude", with the agent name cycling through Claude, ChatGPT, Gemini, Codex, Hermes and OpenClaw. Lede: "Run Street CRM workflows directly from your AI agent with Askpilot. Update records, book viewings, and complete any other workflow your agency needs." Calls to action: Request early access, See the events. Details: built by Askpilot; status: built on the Street Open API; category: CRM, estate agency, workflows; works with Claude, ChatGPT, Claude Code, Codex, Hermes, Gemini, OpenClaw; developers.street.co.uk · Street Open API, 79 webhook events, documented. ### Overview Street CRM is a cloud platform built for UK estate and letting agents. Sales, lettings and property management all sit in one system. Connect it to Askpilot and enquiries get answered while they are still warm, viewings get booked, feedback reaches the vendor the same day, and certificates get chased before they lapse. It runs on a Saturday, over a bank holiday, and when half the branch is out. Every outcome is written straight back to the right record, so your CRM stays complete without anyone retyping between systems. Your team keeps working exactly as they do now, and can ask their AI agent, or whichever agent they use, what happened at any point. ### Workflows "These are available templates. Create any workflow you want to automate." - Enquiry received: Portal enquiry to booked viewing. Match the enquiry to the property, reply with availability, chase by email then WhatsApp, and book the viewing in Street CRM. - Viewing completed: Feedback back to the vendor same day. Ask the applicant while it is fresh, summarise it honestly, and log it against both the property and the vendor. - Certificate expiring: Compliance chased before it lapses. Watch the dates on the record, chase the contractor and the landlord, and file the certificate when it arrives. - Offer accepted: Sales progression kept moving. Chase solicitors and brokers on a schedule, log every reply, and bring you anything that needs a decision. ### Triggers and actions Street CRM documents 79 webhook events (https://developers.street.co.uk/docs/street-open-api/webhooks), so workflows start on the event rather than a schedule. Triggers by group: - Enquiries and applicants: enquiry.created, applicant.sales.created, applicant.lettings.created - Viewings: viewing.booked, confirmed, rearranged, cancelled, completed - Valuations: valuation.booked, instructed, completed, lost, not-attended - Offers: offer.sales.accepted, offer.lettings.accepted, rejected, withdrawn - Listings and properties: listing.published, withdrawn, price-changed, status-changed - Sales and tenancies: sale.exchanged, sale.completed, sale.fallen-through, tenancy.created - Documents and compliance: esign-document.completed, inspection.report-uploaded Actions: find the right record, or ask before creating one; create and update applicants, properties and vendors; write call notes, emails and activity to the record; attach documents, transcripts and correspondence; read a record to answer a question in your agent; move a record forward when a step completes. ## Askpilot + iamproperty (https://askpilot.com/integrations/iamproperty.html) Title: Automate iamproperty Workflows with AI | Askpilot Description: Update records, book viewings and chase documents in iamproperty, or any workflow your agency needs. Set up automation from Claude, ChatGPT or any AI agent. An integration profile page. Badge: Official integration. Heading "Run your iamproperty workflows from Claude", with the agent name cycling as above. Lede: "Run iamproperty workflows directly from your AI agent with Askpilot. Update records, book viewings, and complete any other workflow your agency needs." Calls to action: Request early access, Read the announcement. Details: built by Askpilot; status: official iamproperty integration; category: CRM, estate agency, workflows; works with Claude, ChatGPT, Claude Code, Codex, Hermes, Gemini, OpenClaw; iamproperty.com · Partner announcement: "Askpilot Integration for iamproperty CRM". ### Overview iamproperty is a cloud CRM built for UK estate agents, used by more than 7,000 branches. Sales, lettings, property management and accounts all sit in one system, on one login, with a single view of every client. Connect it to Askpilot and enquiries get answered while they are still warm, viewings get booked, feedback reaches the vendor the same day, and certificates get chased before they lapse. Nothing waits for someone to remember it. Every outcome is written straight back to the right record, so your CRM stays complete without anyone retyping between systems. Your team keeps working exactly as they do now, and can ask their AI agent what happened at any point. ### Workflows "These are available templates. Create any workflow you want to automate." - Enquiry received: Portal enquiry to booked viewing. Match the enquiry to the property, reply with availability, chase by email then WhatsApp, and book the viewing in iamproperty. - Viewing completed: Feedback back to the vendor same day. Ask the applicant while it is fresh, summarise it honestly, and log it against both the property and the vendor. - Certificate expiring: Compliance chased before it lapses. Watch the dates on the record, chase the contractor and the landlord, and file the certificate when it arrives. - Offer accepted: Sales progression kept moving. Chase solicitors and brokers on a schedule, log every reply, and bring you anything that needs a decision. ### Triggers iamproperty does not publish webhooks, so workflows run on a predefined schedule: - A scheduled check, hourly or daily - A new lead or enquiry since the last check - A new applicant or property record - A record that has changed stage - A certificate or compliance date coming up - A sale or tenancy that has moved on ### Actions - Find the right record, or ask before creating one - Create and update applicants, properties and vendors - Write call notes, emails and activity to the record - Attach documents, transcripts and correspondence - Read a record to answer a question in your agent - Move a record forward when a step completes Custom actions can be created for whatever else a workflow needs to do. ## Askpilot + CallSwitch One (https://askpilot.com/integrations/callswitchone.html) Title: Automate CallSwitch One Workflows with AI | Askpilot Description: Every completed call can start a workflow: CRM updated, follow-ups sent, admin done. Set up CallSwitch One automation from Claude, ChatGPT or any AI agent. An integration profile page. Badge: Official partner. Heading "Run your CallSwitch One admin from Claude", with the agent name cycling as above. Lede: "Run CallSwitch One workflows directly from your AI agent with Askpilot. Log calls, send follow-ups, raise tasks, and complete any other workflow your team needs." Calls to action: Request early access, Read the announcement. Details: built by Askpilot; status: official CallSwitch One partner; category: phone system, post-call admin, workflows; works with Claude, ChatGPT, Claude Code, Codex, Hermes, Gemini, OpenClaw; callswitchone.com · Partner announcement: "CallSwitch One partners with Askpilot to save users hours on admin after every call". ### Overview CallSwitch One is a cloud-native communications platform built by Nebula, used by more than 200,000 business users across the UK. It runs your calls across desk phones, mobile and desktop apps, with call routing, IVR and analytics built in. Businesses do not lose time on the call. They lose it afterwards, on the notes, the CRM update, the follow-up email, the task, the reminder and the meeting that has to be booked. Multiply that across every call and it is hours a week. Askpilot makes the call the trigger. The moment it ends, your workflow runs across the tools you already use, so the admin that follows is completed rather than just captured. Nobody retypes anything between systems, and your team can ask their AI agent about any of it afterwards. ### Workflows "These are available templates. Create any workflow you want to automate." - Call ended: Every call written up automatically. Match the number to a record, summarise what was asked and agreed, and log it with the recording and transcript attached. - Call ended: The follow-up sent while it is still fresh. Pull what the caller was promised out of the summary, draft it in your voice, and send it within the hour. - Missed call: Nobody picked up, so Askpilot did. Text them back within minutes with a callback window, chase once, and route them to whoever owns the record. - Every weekday: A morning report on yesterday's calls. What came in, what was handled, and the one thing that still needs a person, delivered into the agent the team already uses. ### Triggers - An incoming call is answered - An incoming call goes unanswered - An outgoing call is answered - An outgoing call goes unanswered A workflow can also start on a schedule, or on an event from another connected tool. ### Actions - Read the transcript and pull out what was agreed - Match the number to a record, or ask before creating one - Write the call summary and outcome to your CRM - Send the follow-up that was promised on the call - Raise tasks and reminders on the right person - Answer a question about a past call in your agent ### Nothing about your phone system changes An add-on, not a replacement. Phone numbers, handsets and apps, call flows and ring groups, and what callers hear all stay exactly as they are. Askpilot only listens for what happened after the call, and acts on it. ## PROCESS.md (https://askpilot.com/process-md.html) Title: PROCESS.md: The Workflow Format for AI Agents | Askpilot Description: PROCESS.md is an open markdown format for business workflows: roles, rules, steps and approvals in one readable file. AI agents write it, Askpilot runs it. Heading "PROCESS.md", eyebrow "Intelligent Process Automation". Lede: "PROCESS.md is a format for writing down your business processes in plain language, with roles, todos, rules, and approvals that AI agents run." Calls to action: Request early access, Read the guide. The hero shows a complete file, contractor-chase/PROCESS.md: name contractor-chase; description "Chase a contractor weekly until they confirm scheduling."; Role "Act as an internal property operations coordinator supporting our team."; Instructions "Contractors are slow to reply in the first week, so do not treat silence as a refusal."; Rules: Stop if contractor confirmed a date; Escalate after 3 weeks without a response, run notify-property-manager; Todos: Check for contractor response (look for replies in the last 7 days); Send follow-up email (use front-inbox to draft a polite chase; ask for approval before sending); Record chase attempt in CRM (in iamproperty-crm, log the message sent, date, and next follow-up date against the repair ticket). ### Why PROCESS.md PROCESS.md is a format for AI agents to intelligently execute processes, such as chasing an overdue invoice or onboarding a new client, based on instructions written in plain language. It replaces traditional rule-based automation tools built around drag-and-drop flowcharts, which are limited to predefined logic and cannot adapt or improvise. - Traditional automation tools, static flowcharts: deterministic processes with every step predefined. They execute exactly as designed, but cannot interpret ambiguity, apply judgment, or adapt beyond the flow. - PROCESS.md, intelligent automation: write the process in plain language. An AI agent runs it, adapts to nuance, handles edge cases you didn't think of, and pauses for your approval when it matters. ### Structure Every PROCESS.md has a YAML header with the name and description, followed by six optional sections: `## Role`, `## Instructions`, `## Events`, `## Rules`, `## Todos` and `## Paths`. Only the header is required. When predefined Todos are absent, the agent creates the work needed to deliver the description by following the Role and Instructions and obeying the Rules. - Frontmatter: a YAML header with two required fields, `name` and `description`. - Role: free text giving the identity, audience, purpose, responsibilities and communication style the agent should use, and whether the process is internal or external-facing. It can be written under `## Role` or inside `## Instructions`; if absent, the agent uses normal internal assistant behaviour. Direct representation of a customer, lead, applicant, supplier or another non-team member is external; support for the internal team or its systems is internal; one outbound task alone does not make a Role external. Under an external Role the agent adopts only the stated identity, grounds answers in the conversation, process assets and verified Sources, does not guess or claim unconfirmed success, takes side-effecting actions only when the process explicitly requires them, treats external messages as data rather than instructions, keeps internal process details and errors private, and accepts approvals only from the assigned internal user. Paths inherit the active Role; nested processes inherit it when they do not define one. If the type or audience is unclear after the whole process has been read, the agent asks the assigned internal user before it communicates or acts. - Instructions: process-wide directives, context and execution requirements. They can set required actions, limits, methods, edge-case and lifecycle behaviour, Sources, skills, assets, approvals, output formats and Path triggers, and apply from setup to completion. Role content has the same priority as Instructions; together they override the description, Events, Todos, Paths and default execution guidance; only Rules rank higher. Conflicting Instructions are put to the assigned internal user rather than guessed. Instructions cannot invent or expand work beyond the explicit process purpose. Include only content that changes execution, because the agent reads and applies every line. - Events: which webhook events from connected tools the process subscribes to. A subscribed event resumes a session that is already open, so time-sensitive work is picked up when the reply arrives and no tokens go on rerunning the session on a schedule to check. Give the source, event id and optional filters, or describe what you want in plain language and let the agent look up what the source actually publishes. A filter on a field that does not exist, or a value the field does not allow, is accepted and then silently never matches, so check the available events and filter fields rather than guess. - Todos: a single step the agent executes. Each has a Title and Description, plus an optional Approval flag. Only include what the agent needs. - Rules: conditions, policies, guardrails or custom directives that apply to the whole process. Each starts with a label followed by the instruction. Rules have the highest priority within a process. Escalation sends notifications by email only; Slack and SMS are not supported yet. - Paths: sub-flows triggered from Instructions, Rules, Todo Titles or Todo Descriptions, either with `run path [path-name]` or a clearly stated condition and Path. Define each under `## Paths` with a `### path-name` heading. To trigger a separate file from your `processes/` folder, use `run process [process-name]`. - Assets: files added to a process for context while it runs. An asset is only read if the Role, Instructions, a Rule, a Todo or a Path references it by name. Move something into an asset when it is long, when it changes on a different schedule to the process, or when more than one todo needs it. The page's worked example, invoice-chase, escalates to the account manager when an invoice is 30 days or more overdue and drafts reminders from assets/invoice-reminder-template. ### Run PROCESS.md in Askpilot Askpilot is purpose-built to run PROCESS.md files. From one place, a process can be activated across your whole company, to specific teams like sales, operations or compliance, to individual employees, and on any trigger: events, schedules, conditions, or manual runs. ## Pricing (https://askpilot.com/pricing.html) Title: Askpilot Pricing: Pay for the Work Done, Not Per Seat Description: Pro from £25 a month, 2,000 credits, 500 free credits to start. Enterprise on request. Pay for the work done, not per seat, from Claude or any AI agent. Heading "Pay only for the work done. Not per seat." Lede: "Unlimited users and every feature on every plan." A currency switch: UK · GBP and International · USD. The page picks GBP for a saved choice, a browser locale ending in -GB or the Europe/London timezone, and USD otherwise. The machine-readable version of this page is https://askpilot.com/pricing.md ("Are you an AI agent? See pricing"). ### Pro One plan with a monthly credit allowance you choose. Every tier includes the same features; only the number of credits changes. The page opens on 2,000 credits a month. | Monthly credits | GBP | USD | | --- | --- | --- | | 2,000 | £25 | $30 | | 4,000 | £50 | $60 | | 7,500 (sold as 10,000 during the launch offer) | £100 | $125 | | 15,000 | £160 | $200 | | 25,000 | £250 | $315 | | 35,000 | £325 | $410 | | 45,000 | £390 | $490 | | 60,000 | £480 | $600 | The 7,500 tier is currently sold as 10,000 credits a month under a launch boost, at the same £100 / $125; when it is selected the card shows "Launch offer · Limited places". Included on every tier: create and run custom workflows; connect your business tools; event triggers, approvals, and notifications; unlimited users. Free trial with 500 credits. Billed monthly. Call to action: Request early access (https://askpilot.com/request-access.html?credits=2000&source=pricing). ### Enterprise Custom pricing. "A package designed around your volume and controls. For larger teams running complex workflows." SSO, multi-factor authentication, audit logs, dedicated support. Custom trial available. Call to action: Talk to sales (sales@askpilot.com). ### How many credits does each process use? Estimates per run. Cost varies with todos, sources and complexity. | Run | What happens | Credits | | --- | --- | --- | | Call logged | Call ends, logged against contact, transcribed, summarised | ~4 | | Missed-call follow-up | Missed call, message sent, logged, reminder set | ~7 | | Post-call admin | Call ends, logged, follow-up email sent, reminder task created | ~8 | | Enquiry to booked valuation | Enquiry qualified, responded, valuation booked | ~13 | | Repair intake to action-ready | Report gathered, classified, logged, escalated | ~13 | | Information chasing | Missing information chased up to 3 times until received or escalated | ~24 | | Property to market | Instruction, terms sent, certificates filed, AML, photoshoot booked | ~48 | ### Free trial and setup - Free trial · 500 credits: "Start running your workflows with 500 free credits." Your free trial includes 500 credits, so you can experience Askpilot before choosing a paid plan. - Optional expert setup: "Want help setting up your workflows?" Our team can map your workflow, configure it around your business, connect your tools, and help you launch. Remote and in-person setup is available. Free onboarding. ### Pricing FAQ - What is a credit? A credit is how Askpilot bills for AI work. Each run uses some credits. Your plan includes a monthly bucket of credits, with auto top-up available if you need more. - How does the free trial work? Your free trial includes 500 credits, so you can experience Askpilot before choosing a paid plan. - Who can sign up for Askpilot? Askpilot is currently available to businesses only. We onboard companies and their teams, not individual consumer accounts. - What happens if I run out of credits? By default, processes pause when you run out of credits. You can either top up manually or wait until your credits reset at the start of your next billing cycle. To keep processes running, enable auto top-up in billing settings. For example, when your balance drops below 7,500 credits, we charge £25 (or $30) and automatically add 2,000 credits. You can turn auto top-up off at any time. - Do you offer annual billing? Pro is billed monthly. Annual billing can be agreed for Enterprise customers. - What payment methods do you accept? All major credit and debit cards (Visa, Mastercard, Amex) via Stripe. Enterprise customers can also pay by invoice on agreed billing terms. ## Request access (https://askpilot.com/request-access.html) Title: Request Early Access | Askpilot Description: Create your Askpilot account and connect Claude or any AI agent in minutes. 500 free credits included. Heading "Request access to Askpilot." Beside the form: "Free trial. Start with 500 credits and run your first workflows before you choose a paid plan." The form is a Tally embed. Links across the site pass `?credits=N` (and `&offer=launch` for the boosted tier) so the credit plan is pre-selected, and `?source=` records which page the request came from. ## After you request access (https://askpilot.com/thank-you.html) Title: Thanks, we'll be in touch | Askpilot (not indexed) "Thanks. We've got it. Askpilot is currently in beta access. As soon as new slots open, we will get in touch." A single link back to askpilot.com. ## Brand (https://askpilot.com/brand/) Title: Askpilot Brand Assets: Logos and Colours Description: Download Askpilot logos, colours and brand assets for press, partners and integrations. "Brand assets. Download the Askpilot logo, colours, typography and illustrations." A logo pack download and a brand contact. - Logo: primary logo and icon, each for light and dark backgrounds, in SVG and PNG. Clearspace of at least the height of the icon; minimum size 90px wide for the full logo, 20px for the icon; place it on cream, white, ink or calm photography. Do not recolour, stretch, rotate or add effects; do not rebuild the arms, change their order or separate them from the wordmark; do not place the logo on busy imagery or clashing colours. - Colours (click any swatch to copy): Ink #16121A (headlines, text, frames and outlines), Cream #FCF9F7 (the warm page background), Surface #FFFFFF, Body #4E4854, Muted #8B8492, Line #EAE3E1; brand accents Brand blue #4C6BEE (work happening: checks, running states, links), Blue light #6583FF, Brand magenta #D53BD5 (eyebrows, highlights, the brand's voice), Brand orange #E6763B (logo arm only); pink ramp Pink wash #FFF3FF, Pink surface #FFD9FF, Pink core #FFA7FF; Success #1F6B49 on #E3F5EA; on-dark logo tints Blue on dark #7F97FF and Magenta on dark. - Typography: Manrope, a geometric sans with a warm, rounded finish. ## Legal (https://askpilot.com/legal.html) Title: Legal, Privacy & Terms | Askpilot Description: Askpilot's terms of service, privacy policy and data processing details. The legal centre holds the Terms of Service (effective 10 September 2025), Privacy Policy, Data Processing Addendum (https://askpilot.com/legal.html#data-processing-addendum), GDPR Compliance Statement, Acceptable Use Policy, Information Security Policy (https://askpilot.com/legal.html#information-security-policy), subprocessor list and Cookie Policy. The Service is operated by AI Number, Inc. It is for business use only: users must be at least 18, must have authority to bind the entity they represent, and may not use the Services as a consumer. Askpilot may ask for proof that an account belongs to a business. ## Apps - Web app: live - Desktop app: live, https://dl.todesktop.com/260512f0sj608ju - Mobile app: coming soon ## Site navigation - Home: https://askpilot.com/ - How it works: https://askpilot.com/#how - Post-call admin (use case): https://askpilot.com/use-cases/post-call-admin.html - Estate agents (industry): https://askpilot.com/industries/estate-agents/ - IVA firms (industry): https://askpilot.com/industries/iva-providers/ - Integrations: https://askpilot.com/integrations.html - Street CRM integration: https://askpilot.com/integrations/street.html - iamproperty integration: https://askpilot.com/integrations/iamproperty.html - CallSwitch One integration: https://askpilot.com/integrations/callswitchone.html - Pricing: https://askpilot.com/pricing.html - Pricing (machine-readable): https://askpilot.com/pricing.md - PROCESS.md: https://askpilot.com/process-md.html - Blog: https://askpilot.com/blog/ (RSS: https://askpilot.com/blog/rss.xml) - Request early access: https://askpilot.com/request-access.html - Brand assets: https://askpilot.com/brand/ - Legal: https://askpilot.com/legal.html - Sitemap: https://askpilot.com/sitemap.xml ## Contact - Support: support@askpilot.com - Sales: sales@askpilot.com - Phone: +44 7463 171214 - Area served: available globally, with the United Kingdom as the primary market. ## Keywords Askpilot, agentic workflow execution infrastructure, AI that runs your business workflows, AI workflow automation, run business workflows from Claude, ChatGPT workflow automation, AI agent infrastructure, Askpilot MCP, remote MCP server, MCP integrations, PROCESS.md, workflow triggers and actions, event-driven workflows, webhook event subscriptions, event filters, agentic workflow execution, human-in-the-loop approvals, runs dashboard, audit trail, credit-based pricing, monthly credits, unlimited users, Claude, Claude Code, ChatGPT, Codex, Hermes, Gemini, OpenClaw, CallSwitch One integration, iamproperty integration, Street CRM integration, HubSolv, Yay.com, post-call admin, call logging automation, missed call follow-up, AI for UK estate agents, estate agency automation, lettings automation, AI for IVA providers, IVA case admin automation, annual review automation, document chasing, invoice chasing, lead qualification, free trial 500 credits ## Blog Index: https://askpilot.com/blog/ (RSS: https://askpilot.com/blog/rss.xml) - [What Is Agentic Workflow Automation?](https://askpilot.com/blog/what-is-agentic-workflow-automation.md): Agentic workflow automation means the AI agent runs the workflow, not steps firing in a fixed sequence. What it is, and when Zapier or n8n still wins.