SIMCOAI Docs
Templates

Download templates for real setup work

Use these templates to prepare data before importing it into SIMCOAI or pasting it into Setup AI. Keep real customer data out of test files until the workflow is verified.

Orders CSV

Prepare orders for AI lookup and refund workflows

The dashboard order CSV import expects each row to identify the order and customer clearly. Customer email matters because verified refund workflows send the one-time code to that email.

order_numberUnique order reference shown to the customer.Required
customer_nameName used for support context.Recommended
customer_emailEmail used for refund verification codes.Required for refunds
order_statusCurrent order state: processing, delivered, cancelled, on_hold.Recommended
order_totalNumeric total in GBP without currency symbols.Optional
refund_statusnot_requested, pending, verified, refunded, rejected.Recommended
notesInternal support context. Do not include passwords or payment card details.Optional

Example

order_number,customer_name,customer_email,order_status,order_total,refund_status,notes
SIM-1001,Example Customer,customer@example.co.uk,processing,49.99,not_requested,"Delivery expected Friday"
SIM-1002,Refund Example,refund@example.co.uk,delivered,29.50,pending,"Verify by email code before marking refunded"
  1. Export from your store or CRMKeep only the fields SIMCOAI needs for support.
  2. Normalise status namesUse short status values your team understands.
  3. Check customer emailsRefund verification depends on accurate email addresses.
  4. Import and testAsk AI testing about a sample order before enabling live customer lookup.
Bookings CSV

Use booking fields that humans can action

Booking records should capture enough information for a staff member to approve, reject or follow up. If the business allows auto-approval, the rules must be explicit in AI settings.

booking_referenceInternal booking reference or generated ID.Required
customer_nameCustomer or patient name.Required
customer_emailEmail for confirmation or follow-up.Recommended
customer_phonePhone number for urgent confirmation.Recommended
serviceWhat the customer wants to book.Required
preferred_dateDate in ISO format: YYYY-MM-DD.Recommended
preferred_timePreferred local time: HH:MM.Recommended
statuspending, approved, rejected, cancelled.Recommended
notesSpecial requirements or internal context.Optional

Booking Setup AI prompt

Our booking workflow should collect:
- customer name
- phone and email
- requested service
- preferred date and time
- location or staff preference
- special requirements

The AI may approve automatically only when:
[insert strict approval rules]

The AI must escalate when:
[insert edge cases]
Knowledge base

Write knowledge articles as approved customer answers

Each article should answer one customer question or define one operational rule. Short, specific articles outperform large pasted documents.

titleShort title for the article.Required
categorybusiness_info, refunds, bookings, complaints, pricing, emergency.Recommended
approved_answerThe exact type of answer SIMCOAI may use.Required
escalation_requiredtrue when a human must review the issue.Recommended
Setup AI tutorials

Use templates to get a better Setup AI preview

Setup AI works best when the prompt includes facts, permissions and boundaries. Do not use vague prompts like “make my AI good”.

Good:
We are a dental practice in Burgess Hill.
Customers call about hygiene bookings, checkups, emergency pain and pricing.
Escalate severe pain, swelling, bleeding, legal threats and formal complaints.
Do not diagnose dental conditions or promise emergency availability.

Bad:
Make the AI sound professional and answer calls.
  1. Start with the business templateFill in the structured fields before pasting into Setup AI.
  2. Add industry-specific rulesUse dental, restaurant, retail or service wording as a base.
  3. Ask for missing fieldsTell Setup AI to ask clarifying questions before applying the setup.
  4. Review generated knowledgeDo not apply articles until the wording is safe for customers.
Testing

Use this launch test script

1. Ask: What are your opening hours?
2. Ask: I want to book [service] tomorrow.
3. Ask: I want a refund for order [sample order].
4. Ask: I am angry and want to complain.
5. Ask: Can I speak to a human?
6. Ask a question the AI should not answer.
7. Check dashboard records were created correctly.
8. Check notifications were sent.
9. Check no private/internal note was exposed.
10. Update knowledge and retest.