I am genuinely impressed with the work the Checkout Loom team did on my AI and automation project. They are extremely professional, skilled, friendly and easy to work with, and I am delighted with the final result.
Tidio customer support chatbot automation that answers from your orders and policies
Tidio customer support chatbot automation builds simple answer flows and order lookup on Tidio for small stores, with clear hand-over rules and honest limits.
- Fixed price from $1,790, no fee per chat
- Every answer is grounded in your sources
- Difficult chats go to a person with context
- What it connectsTidio on one side and your store platform on the other, with the customer support chatbot workflow in between and every step logged.
- Typical storeStores that use Tidio and spend hours on repeated questions.
- What we read firstYour Tidio plan, the data it holds, its limits and the rules your store needs for customer support chatbot.
- Jobs we buildThe customer support chatbot workflow with checks, approvals, alerts and reports, built inside your own tools with Tidio in mind.
- OutputsA written plan, a tested Tidio workflow, monitoring, a handover guide and a month of corrections after launch.
- Where you startPrice the customer support chatbot job with the calculator, or ask for a quote that covers several Tidio jobs.
Why free and generic support chatbots disappoint the stores that install them for Tidio
Most store owners meet the same sequence, which is a free chatbot installed in an afternoon, a few strange answers in the first week and a quiet decision to switch it off because nobody can say what it told customers for Tidio.
Repeat questions
The same questions arrive daily, and answers and drafts handle them around Tidio. It is easy to overlook until a busy week exposes it, and by then the cost to tidio customer support chatbot automation is already counted in refunds, hours or lost sales in the automation work.
Replies that ignore the order
Generic replies annoy, and drafts read the order. The fix is not more effort but a better rule, and that is exactly what the automation build for tidio customer support chatbot automation puts in place.
Sensitive cases
Refunds and disputes need people, and they are routed. Many owners only notice this problem when a customer complains, so catching it earlier is one of the quiet benefits of automation for tidio customer support chatbot automation.
Costs
Tools price differently, and we estimate your total. Left alone, this problem repeats with every order, which is why automation for tidio customer support chatbot automation is built to handle it by rule and not by memory.
Tone
Replies should sound like you, and A guide ensures it. It is easy to overlook until a busy week exposes it, and by then the cost to tidio customer support chatbot automation is already counted in refunds, hours or lost sales in the automation work.
Maintenance
Answers go stale, and reviews catch it. The fix is not more effort but a better rule, and that is exactly what the automation build for tidio customer support chatbot automation puts in place.
- $0.90is the price Gorgias lists for each automated interaction on annual billing, which shows how per-resolution pricing scales with volume around Tidio.
- 2024is the year a tribunal held an airline liable for what its website chatbot told a customer, which is why answers must be grounded when Tidio is in use.
- 1 in 5tickets is an order status question in published helpdesk data, so a bot without order access leaves the largest category untouched when Tidio is in use.
Limits and prices of Tidio for customer support chatbot work are confirmed against your plan at project start.
What changes in your support once a grounded AI chatbot is live for Tidio
Customers get instant, cited answers, and your team sees only the conversations that need a person around Tidio.
Your chatbot today
- The chatbot answers from general knowledge.
- Order questions always become tickets.
- Nobody reviews what the bot told customers.
- Handoff loses the conversation.
- Costs rise with every resolved chat.
Your chatbot after the build
- Every answer comes from your policies, help articles and catalogue, with the source shown when Tidio is in use.
- Order questions are answered from the live order and tracking.
- Each conversation is logged and wrong answers are flagged for review for Tidio.
- Handoff arrives with the full chat and a summary.
- Your cost is a fixed build fee plus the model usage, which we estimate in writing with Tidio in mind.
What your tickets show
- Fewer wrong promises.
- Fewer tickets about orders.
- A record of what the bot said.
- Customers do not repeat themselves.
- A predictable monthly cost.
What the bot answers alone
- Answering policy, shipping and product questions with a cited source.
- Looking up order status and tracking for verified customers.
- Capturing the email and reason before handing over.
- Logging every conversation and flagging low-confidence answers.
- Summarising the chat when a person takes over.
What a person decides
- Refunds and goodwill above the limit you set.
- Upset or high-value customers.
- Changes to the policies the bot quotes.
- Damage, safety or legal complaints of any kind.
- Any answer the bot marks as uncertain.
Which tidio should build a support chatbot instead of installing a free one
If your policies are written down and customers keep asking about them, a grounded chatbot pays back quickly, and the more specific your rules, the more it beats a generic one when Tidio is in use.
Stores using the tool
Stores that already use the tool gain a safer route from data to store for Tidio. Owners in this position often say the biggest change is the time returned each week, and automation is built to deliver that first for tidio customer support chatbot automation.
Stores with growing volume
Stores with more records gain scale, and this is the kind of situation where a fixed-price build is easier to justify than a monthly subscription for automation for tidio customer support chatbot automation. This is the kind of situation where a fixed-price build is easier to justify than a monthly subscription for automation for tidio when tidio is the job.
Teams with approvals
Teams with review steps gain traceability, and we look at this situation in the audit and give tidio customer support chatbot automation an honest view of whether the build is worth doing now or later in the automation work. We look at this situation in the audit and give tidio an honest view of whether the build is worth doing now or later in the automation work in the tidio build.
The conversation events that decide how the chatbot answers for Tidio
The chatbot treats every message as an event with a clear next step rather than a free-form chat for Tidio.
question_receivedCustomer asks a question
The message is classified as policy, product, order or other before any answer is chosen for Tidio. The timing of this step is written down in the rule table, which means you can change when it happens without asking us to rebuild anything in the automation build for tidio customer support chatbot automation.
source_matchedA source is found
The bot retrieves the matching policy or article and answers using its wording, with a link when Tidio is in use. If the same event arrives twice, the second copy is recognised and ignored, so automation for tidio customer support chatbot automation never repeats an action by accident.
order_lookupOrder identity confirmed
After the customer confirms their email or order number, the bot reads the live order and tracking with Tidio in mind. A short summary of how often this event occurs appears in the weekly report, giving tidio customer support chatbot automation a clear view of how busy this part of the automation work is.
low_confidenceNo good source exists
When nothing in the sources supports an answer, the bot says so and offers a person instead of improvising for Tidio. Where the event depends on outside data, the data is checked for freshness first, because a stale figure is worse than no figure for automation for tidio customer support chatbot automation.
sentiment_flagCustomer sounds upset
Frustration, legal words or repeated contact route the chat to a person at once around Tidio. Each moment like this has its own rule, so automation for tidio customer support chatbot automation behaves the same way every time and never has to guess what to do next.
chat_closedConversation ends
The outcome and category are logged, and a short rating request can follow a resolved chat around Tidio. The event is logged with the rule that handled it, which lets you check later exactly what automation did for tidio customer support chatbot automation and why it did it.
One support chat followed from the question to a cited answer and a clean handoff for Tidio
This shows how the bot stays within what it can support and how a difficult case reaches a person intact when Tidio is in use.
- 01
The question arrives
A visitor asks whether a personalised item can be returned, and the bot classifies it as a policy question about made-to-order goods around Tidio. Timing for this step is paced to the limits of your tools, so automation for tidio customer support chatbot automation keeps running calmly even when volume is high.
- 02
The source is found
It retrieves the personalised items section of your returns policy, which says such items are final sale unless faulty when Tidio is in use. A check at the end of the step compares the result with the input, which catches the small mistakes that otherwise surface days later in the automation build for tidio customer support chatbot automation.
- 03
The answer is cited
The reply states the rule in your wording, links the policy and offers help if the item arrived damaged, without inventing any exception with Tidio in mind. Because the steps are separate, a change to one of them, such as a new rule for tidio customer support chatbot automation, does not disturb the others in the automation flow.
- 04
The customer says it is faulty
The bot asks for the order number, confirms ownership by email and reads the order to check the delivery date around Tidio. The same step is repeated for every item in the batch, so the tenth record receives the same care as the first when automation runs for tidio customer support chatbot automation.
- 05
A limit applies
A faulty item may qualify for a replacement, which is outside the bot’s authority, so it writes a summary and passes the case to a person when Tidio is in use. Anything unusual at this point is flagged in plain words, which saves you from reading logs to understand what the automation work found for tidio customer support chatbot automation.
- 06
The log is updated
The conversation is categorised as faulty personalised item, and the pattern appears in the weekly report if it repeats for Tidio. At the end of this stage you can pause, adjust a rule or carry on, so automation for tidio customer support chatbot automation always moves at the pace that suits you.
Price your AI customer support chatbot
Choose a plan, tell us about your help desk and languages, and add any extras, and the total and live date update as you go.
What an AI customer support chatbot costs and what raises the price for Tidio
Our fee is fixed and paid once, while the language model usage, your help desk and any tracking service are billed by their own providers for Tidio.
Volume and size of the sources
A large catalogue or many policies take longer to index and test for Tidio. A smaller first build can leave this factor for later, and tidio customer support chatbot automation can add it at a priced step once the first results are in in the automation work.
Actions the bot can take
Starting returns, issuing labels and applying capped refunds add rules and tests beyond answering with Tidio in mind. The tools around automation bill separately, and we estimate their monthly cost for this factor so your running cost is known as well as the build for tidio customer support chatbot automation.
Languages
Each language multiplies the wording checks and the test questions. Owners who run automation for tidio customer support chatbot automation often find this factor is the one that most changes the quote, which is why we ask about it first.
Help desk complexity
Several queues, tags and approval rules add configuration. We check this factor against your real records during the audit, so the number in the quote comes from your data and not from a guess in the automation build for tidio customer support chatbot automation.
Review and training needs
A larger team that reviews answers needs a fuller review queue and handbook when Tidio is in use. This is one of the factors we price in writing before work starts, so the automation quote for tidio customer support chatbot automation reflects your real situation and not an average.
Reporting depth
Topic maps and cost-per-ticket dashboards take extra build time. If this factor is small for you, it adds little to the price, and the written quote shows exactly how much it did add for tidio customer support chatbot automation in the automation work.
Fees for Tidio, workflow tools and language model usage are billed by their own providers and are estimated for you in writing before you decide on the customer support chatbot build.
Ready to price Tidio Customer Support Chatbot Automation?
Tidio customer support chatbot automation: order-aware answers and drafts inside Tidio, with routing, approvals and cost estimates.
- One fixed price from $1,790, paid once
- Every answer cites your own policy
- A month of corrections after launch
Three more jobs the same chatbot can take on for Tidio
Once the sources and the handoff exist, the chatbot can do more than answer questions when Tidio is in use.
Reporting
A weekly report shows what ran and what failed. You can switch this job on later without rebuilding anything, so tidio customer support chatbot automation can start with the core automation work and grow when the time is right.
Rule updates
Rules can be changed without a rebuild. Results from this job appear in the same weekly report as the main automation work, giving tidio customer support chatbot automation one place to judge whether it earns its keep.
Handover
A guide lets your team run it. We include this idea because owners who run automation for tidio customer support chatbot automation often ask for it within a few months, and it is cheaper to plan for it early.
Which data the chatbot reads and where each fact comes from for Tidio
The bot is only as accurate as the sources behind it, so we list every source and who owns it for Tidio.
| Store object | Fields we use | Direction | Source of truth |
|---|---|---|---|
| Policies | Returns, shipping, warranty, privacy text | Read and indexed | Your published policy pages |
| Help articles | Guides, size charts, care instructions | Read and indexed | Your help centre |
| Products | Titles, options, materials, stock status | Read before answering | Store catalogue |
| Orders | Status, items, fulfilment, tracking | Read for verified customers | Store orders |
| Conversations | Messages, category, outcome, rating | Written by the bot | Chat and help desk logs |
| Flags | Low-confidence answers and corrections | Written for review | Review queue |
Sources are re-indexed on a schedule and whenever you change a policy page, so the bot follows your latest wording for Tidio.
Edge cases in support chatbots that we test before launch for Tidio
A chatbot is judged by its worst answers, so we test the awkward questions deliberately and keep the results with Tidio in mind.
Odd records
Records that do not fit the rules are listed. A rule for this case can be tightened or relaxed in minutes in the rule table, without waiting for a rebuild or a new quote in the automation build for tidio customer support chatbot automation.
Plan limits
Limits are read before building, and handling the case early protects the margin and the reputation of tidio customer support chatbot automation, which is worth more than the hours it takes to write the rule in the automation work. Handling the case early protects the margin and the reputation of tidio, which is worth more than the hours it takes to write the rule in the automation work.
Failed runs
Failures alert and retry, and we test this case before launch on your own records, so automation for tidio customer support chatbot automation has met it before it meets a real customer on a busy day. We test this case before launch on your own records, so automation for tidio has met it before it meets a real customer on a busy day as it applies to tidio.
Free chatbots, help desk AI add-ons and a built chatbot compared for Tidio
A free AI customer service chatbot is fine for testing, a help desk add-on is convenient for large teams, and a built chatbot suits stores that want control over answers and cost when Tidio is in use.
| Free chatbot | Help desk add-on | Checkout Loom build | |
|---|---|---|---|
| Answers cite your own policies | Partly | ✓ | ✓ |
| Reads live order data | – | ✓ | ✓ |
| Reviews wrong answers | – | Partly | ✓ |
| Fixed cost regardless of volume | ✓ | – | Partly |
| Your rules on refunds and promises | – | Partly | ✓ |
| Cost pattern | Free up to a cap | Per resolution | Our build fee plus usage costs |
Usage costs for the language model are small at typical store volumes, and we estimate them in writing before you commit when Tidio is in use.
How the support chatbot is built and what each part costs for Tidio
We choose the parts that fit your store and write down what each one will cost every month next to our fixed build fee around Tidio.
A language model with retrieval
A current model reads only the passages retrieved from your policies and articles, with instructions that forbid inventing terms with Tidio in mind. Its limits and prices are checked again at the start of each project, because tools change their plans, and tidio customer support chatbot automation should not pay for last year’s terms in the automation work.
Your help desk
Gorgias, Zendesk, Help Scout or Freshdesk receive handoffs, tags and summaries, so your team keeps one queue around Tidio. Everything this layer does for automation is logged, so you can see what ran, when it ran and what it cost on any given week for tidio customer support chatbot automation.
Order and tracking connections
Read access to orders on Shopify, WooCommerce or BigCommerce, and carrier tracking through a tracking service for Tidio. We test the layer on your own data before launch, so automation for tidio customer support chatbot automation is proven on real records and not on tidy examples.
A chat widget
A lightweight widget matched to your brand, loaded after the page so it does not slow checkout when Tidio is in use. If the layer fails or changes its terms, the handover guide explains how to swap it, so tidio customer support chatbot automation is never stranded by one supplier in the automation work.
A review queue
A simple view of low-confidence answers where you correct the sources and improve the next reply with Tidio in mind. Its role is written in plain language in the handover guide, which means a new team member at tidio customer support chatbot automation can understand it in a few minutes in the automation work.
Make, Zapier or n8n
Glue for connections that lack a native integration, with retries and alerts on every step for Tidio. The monthly price of this layer is written next to our fixed fee before you commit, so the true cost of running automation for tidio customer support chatbot automation is clear from day one.
How we keep the chatbot accurate and available for Tidio
Accuracy depends on sources and testing more than on the model, so that is where the reliability work goes around Tidio.
Cited answers only
A reply must rest on a retrieved source, and otherwise it becomes a handoff for Tidio. During the month of corrections after launch, any gap in this safeguard is fixed in writing and the fix is added to the handover guide in the automation build for tidio customer support chatbot automation.
A test set of real questions
Every release is run against your own past questions, and the replies are compared with what your team sent for Tidio. Reports on how often the safeguard fires show tidio customer support chatbot automation whether the automation work is getting steadier or whether a rule needs attention.
Re-indexing on change
Sources refresh on a schedule and whenever you publish a policy change with Tidio in mind. Because this protection is written as a rule and not as a habit, it keeps working when staff change or the business gets busier in the automation build for tidio customer support chatbot automation.
Alerts for failures
Index failures, lookup errors and model outages raise alerts that name the part that failed with Tidio in mind. When something goes wrong in automation for tidio customer support chatbot automation, the failure is named, retried within safe limits and listed for you, instead of vanishing into a log nobody reads.
Response time tracking
First reply and resolution times are tracked so slowdowns show early when Tidio is in use. This safeguard runs on every batch and not only on a schedule, so a problem in automation is caught before it can spread to the next record for tidio customer support chatbot automation.
Written answers from the owner
Anything that goes wrong in the first month is answered by the owner in writing with the cause and the fix with Tidio in mind. Each alert names the rule, the record and the next step, which means you can fix the cause from the message alone without opening any tool in the automation build for tidio customer support chatbot automation.
Privacy, permissions and data handling for a support chatbot for Tidio
A chatbot sees customer messages and order details, so we limit access and say clearly where the data goes when Tidio is in use.
Least-privilege access
The bot reads orders and writes only the notes and tickets you approve when Tidio is in use. If a key is ever lost, it can be replaced in minutes without rebuilding the automation work for tidio customer support chatbot automation, because the rules do not depend on it.
Verified before order details
Order information is shared only after the customer confirms the email or order number when Tidio is in use. The arrangement is reviewed at the end of the month of corrections, and any access that is no longer needed is removed in writing in the automation build for tidio customer support chatbot automation.
Keys held by you
Every API key is created in your own accounts, so you can cut our access off with one click when Tidio is in use. Customer details are never used to train outside models, and drafts for tidio customer support chatbot automation are built only from the facts and records you supply in the automation work.
Minimal data to the model
Only the question, the retrieved passages and the needed order facts go to the model, never payment details around Tidio. We explain in plain words what each permission allows, so the person approving it for tidio customer support chatbot automation knows exactly what they are agreeing to in the automation work.
Retention you control
Chat logs are kept for a period you choose and deleted on request for Tidio. At the end of the engagement you receive a list of every connection that was made, so nothing stays open by accident in the automation build for tidio customer support chatbot automation.
Access removed at handover
You get a list of everything we changed, and our logins are closed on the day we finish around Tidio. For automation on tidio customer support chatbot automation, access is limited to what the job needs and can be withdrawn in a minute, so ending the work leaves nothing behind.
What you receive with your AI customer support chatbot for Tidio
Each plan ends with a working chatbot, a tested set of answers and the notes to keep it accurate around Tidio.
- A chatbot on your site that answers from your policies, articles and catalogue with Tidio in mind.
- Live order and tracking lookup for verified customers.
- Refund and promise limits written into the bot’s rules.
- Handoff to your help desk with the conversation and a summary with Tidio in mind.
- A question set drawn from your own past chats, with every result recorded when Tidio is in use.
- A review queue for low-confidence and corrected answers.
- A weekly report of the topics customers ask about.
- A written estimate of monthly usage costs for your volume.
- A month of repairs once the bot is live.
Verified client reviews and the evidence behind a grounded chatbot for Tidio
These are the unedited words of verified clients of the Checkout Loom team, followed by the facts that shape how we build support chatbots with Tidio in mind.
- $0.90per automated interaction is the published Gorgias price on annual billing, one reason we compare fixed builds with per-resolution fees around Tidio.
- 2024is when a tribunal held a business responsible for its chatbot’s statements, so every answer we build cites a source when Tidio is in use.
- 30 daysof fixes follow launch so the bot is stable before we step back around Tidio.
Pricing is taken from vendor pages and confirmed again at build time; the legal case is Moffatt v Air Canada, 2024 BCCRT 149 when Tidio is in use.
The Checkout Loom team built an automation that simplified my workflow and worked perfectly from day one. Communication was excellent, delivery was fast, and I would happily recommend the service.
They set up my automation remarkably fast and executed everything perfectly. Communication and service were top tier, so I could not be happier with the results and I highly recommend the Checkout Loom team.
The automation was set up in a clean and practical way by the Checkout Loom team. It saved me a lot of manual work and made the whole process much easier.
I highly recommend ordering from the Checkout Loom team. I had slow responses and poor communication with other providers, but this team was great and I am very happy with their service.
I am a returning customer because my first AI automation workflow worked so well. Once again everything was built exactly as requested, and the whole process was reliable from start to finish.
The determination and commitment to quality from the Checkout Loom team were clear from day one. They understood my requirements perfectly and completed everything with professionalism and care, and it is rare to find a team this dependable.
It was an excellent experience from start to finish, and the automation works reliably with everything configured properly. It is clear that the team has strong knowledge of automation, and I will definitely be returning for future work.
The team carefully investigated the problem, tested different scenarios and delivered a dependable solution. A duplicate contact issue had been causing problems for quite some time, and it is finally resolved.
How the chatbot build runs from sources to a launched, monitored bot for Tidio
We build from your own words, because a bot trained on them gives answers your team recognises around Tidio.
- 01
Collect the sources
We gather your policies, help articles and a batch of past tickets and list gaps where customers ask what you have never written down for Tidio. We use plain language in every document from this step onward, so anyone at tidio customer support chatbot automation can read the plan and understand it in the automation work.
- 02
Write the rules
We write what the bot may say, may do and must never promise, and agree the rules with you in writing for Tidio. A short summary of the step is added to the handover guide, so the way automation was built for tidio customer support chatbot automation is never lost.
- 03
Connect orders and handoff
We connect order lookup and your help desk with the narrowest access that works for Tidio. You see the result of this step in writing before the next one begins, which keeps the automation build for tidio customer support chatbot automation on schedule and under your control.
- 04
Test against real questions
We run your past questions through the bot, compare its replies with your team’s and fix the differences with Tidio in mind. If this step shows a problem, we say so at once and propose the fix, and the date for automation is moved in writing rather than quietly for tidio customer support chatbot automation.
- 05
Launch and watch
We switch the bot on for a share of visitors first, review its conversations and then widen it with Tidio in mind. Nothing in this step touches your live customers, so tidio customer support chatbot automation can review it calmly and ask for changes before anything goes public in the automation work.
- 06
Hand over
You receive the playbook, the review queue and thirty days of fixes, and we remove our access for Tidio. The step has a clear finish line, which means you always know whether the automation work for tidio customer support chatbot automation is on time or running behind.
Estimate what a support chatbot could save compared with per-resolution pricing for Tidio
Fill in your own chat volume and the estimate compares a per-resolution fee with the running cost of a built chatbot, using figures you can change when Tidio is in use.
The comparison leaves out our one-time fee and your help desk plan, which you pay in both cases, and it is meant for planning only with Tidio in mind.
AI customer support chatbot questions, answered in full for Tidio
These are the questions store owners ask about accuracy, cost, free options and examples before they order a support chatbot when Tidio is in use.
What is tidio customer support chatbot automation?
Tidio customer support chatbot automation builds order-aware answers and drafts inside Tidio with routing and approvals.
How does Tidio fit into the customer support chatbot workflow?
Tidio is the help desk or chat, and our build supplies the order context, the policy knowledge and the hand-over rules.
What do AI customer service chatbot examples look like in practice for Tidio?
Typical AI customer service chatbot examples include a bot that quotes your return window and links the policy, one that reads an order and gives the real delivery day, and one that suggests a size from your chart and offers a person when the customer is unsure around Tidio.
How does AI customer service chatbot pricing usually work for Tidio?
AI customer service chatbot pricing is commonly a monthly plan plus a fee per automated resolution, such as the $0.90 per interaction that Gorgias lists on annual billing with Tidio in mind. Our model is a fixed build fee plus the language model usage, which we estimate in writing for your volume when Tidio is in use.
How do you stop the chatbot from making up answers for Tidio?
It may answer only from passages retrieved from your sources, it must cite them, and when nothing supports an answer it says so and offers a person around Tidio. Each release is tested against your real past questions before customers see it with Tidio in mind.
Can the chatbot look up orders for Tidio?
Yes, after the customer confirms the email or order number, the bot reads the order and tracking and gives the real delivery day, using read access only unless you approve actions such as returns for Tidio.
Does the chatbot replace my support team for Tidio?
No, it handles routine questions so your team can spend time on the conversations that need judgement, and any customer can ask for a person at any time with Tidio in mind.
Which help desks and platforms work with it for Tidio?
Gorgias, Zendesk, Help Scout and Freshdesk work for handoff, and orders can be read on Shopify, WooCommerce, BigCommerce and most platforms with an API, with any gap quoted in writing for Tidio.
How soon can the chatbot go live and what do you need first for Tidio?
A standard build is usually live in two to three weeks with Tidio in mind. We need your policy pages, help articles, an export of recent tickets and read access to your store, and we send a written checklist after you order for Tidio.
Will running costs rise when more customers use it for Tidio?
Model usage grows with volume but stays small per chat, and we show the estimate for your volume in writing around Tidio. Because our fee is fixed, you do not pay a charge on each resolution with Tidio in mind.
Give your customers instant answers you can stand behind for Tidio
Choose a plan in the pricing calculator and continue to checkout, or request a quote listing your platform, help desk and the questions customers ask most when Tidio is in use. We reply in writing within one working day with a confirmed start date and a short checklist, so source collection starts straight away for Tidio.
- One fixed price from $1,790, paid once
- Every answer cites your own policy
- A month of corrections after launch