Online support for your site, from an assistant that answers by itself
goya24 reads the pages of your site you pick, and connects to WooCommerce, Zarinpal or your own API — so your agent checks the real order and answers, instead of asking the customer to wait.
The problem
Your team answers the same forty questions every day
«سفارشم کی میرسه؟» is not a hard question. It is a slow one — someone opens the order panel, copies a tracking code, checks the post site, comes back, and types an answer. Forty times a day.
Most tickets are lookups, not problems
Where is my order, is this in stock, did my payment go through. Answering them needs data, not judgement — but a chatbot without that data just apologises.
Chatbots don't know anything real
A bot that can only quote your FAQ will confidently invent a delivery date. That costs more trust than it saves time.
Your customers write at 1am
Peak messaging hours are not office hours. Every night your queue grows, and every morning starts behind.
How it works
Point it at your site. It works out the rest.
Four phases, about ten minutes, and the last one is watching it work.
- 1It scans your site
One URL. We crawl your pages and products, detect your framework and platform, and spot the services you already run — WooCommerce, Sazito, Digify, Shopfa, Zarinpal.
- 2It learns your content
Pages are chunked on headings, embedded, and re-crawled on a schedule so answers stay current. Add docs, PDFs, past tickets or a repository.
- 3It gets tools, not just answers
Connected services become callable tools. It checks the real order, tracks the real parcel, verifies the real transaction — and every write action can require your approval.
- 4You watch it reason
Every reply carries its full trace: what it retrieved, which tools it called, how confident it was. When confidence drops below your line, it fetches a human instead of guessing.
Features
The product, piece by piece
Everything the product does, each on a page of its own, with the real screens.
Pricing
How many answers a month do you need?
Every plan is a number of credits a month, and each answer from your agent takes one to four of them, depending on the tier you pick. Start with 100 free credits, then pay for one, three, six or twelve months at a time. What your team writes is never counted.
Month by month, at the full price.
Free
To try it on your real site
100 credits, once per workspace and per mobile number. It does not renew.
- Credits
- 100, once
- Operator seats
- 2
- Knowledge pages
- 500
- Knowledge re-read
- Monthly
- Assistant operations
- 10
Basic
For a shop that is starting out
3,900,000 toman for one month
- Credits
- 500 a month
- Operator seats
- 5
- Knowledge pages
- 500
- Knowledge re-read
- Monthly
- Assistant operations
- 100 a month
Growth
For a team that answers all day
9,900,000 toman for one month
- Credits
- 1,500 a month
- Operator seats
- 10
- Knowledge pages
- 1,500
- Knowledge re-read
- Weekly
- Assistant operations
- 300 a month
Business
For a busy store with several teams
22,900,000 toman for one month
- Credits
- 4,000 a month
- Operator seats
- 20
- Knowledge pages
- 4,000
- Knowledge re-read
- Daily
- Assistant operations
- 1,000 a month
Enterprise By agreement
For high volume, with numbers agreed with you
- Operator seats: Unlimited
- Knowledge pages: Unlimited
- Knowledge re-read: Daily
- Assistant operations: Unlimited
Every paid plan has every channel and every integration. Plans differ only in these five numbers.
One credit is one answer on the light tier. Standard, our recommendation, takes 2 and max takes 4. An answer to a message with a picture counts twice. Your team's replies, hand-offs and failed attempts cost nothing. Unused credits expire when the term ends.
Questions
Before you ask
- What stops it making things up?
- It answers only from what retrieval returned, and cites it. Below your confidence threshold it hands off rather than guessing — you set that line, and you can watch every decision in the trace.
- Where does our data go?
- Crawled content and embeddings stay in your workspace. Personal data is masked before anything is logged. On the Enterprise plan you can run it in your own cloud, or bring your own model keys so text never touches ours.
- Does it work with Iranian services?
- Yes — that is what it was built for. WooCommerce and WordPress for orders and content, Telegram and Bale for chat, email for the inbox — and a Persian agent that reads and writes the way your customers do. More Iranian services join as each is tested with a real account.
- How good is its Persian?
- The whole product is Persian-first, right down to a Persian-tuned embedding model. It replies in whichever language the customer wrote in.
- We already use Intercom or Zendesk.
- Import your resolved tickets as knowledge and the agent starts from how your team already answers. Run it on a slice of traffic first and grow it as you gain confidence.
- How long until it's useful?
- The scan and first index take about ten minutes. Most teams leave it in draft for a day, read the traces, tighten the instructions, then publish.
- How do credits work?
- A credit is one answer from your agent on the light tier. The standard tier, which we recommend, takes 2 credits an answer and max takes 4. The workspace owner picks one tier for the whole workspace. An answer to a message with a picture counts twice. A term's credits all arrive on day one and last until the term ends, and whatever is left then expires. If they run out, the chat stays on and new conversations go to your team. Customers never see a message about it. Your team's replies and hand-offs cost nothing.
- Can I move to a bigger plan mid-term?
- Yes. The new plan starts at once, and the remaining value of your current plan comes off its price: the unused share of what you paid, by credits left or days left, whichever is smaller. To stay on the same plan or move to a smaller one, buy the next term in the last seven days of this one. It starts when this one ends.
Your first agent is ten minutes away
Start on the free plan: 100 credits, no card.