Yes. Add your rates as a pricing page or table. SleekAI uses that matrix to quote ES-EN vs JP-EN vs AR-EN at the right rate without confusing them. The bot can also handle minimum charges, page-based vs word-based pricing, and domain factors like legal or medical surcharges. Most agencies see that 80 percent of their RFQs match a published rate exactly, and the bot quotes them end to end without human review.

Yes. Add your certification policies as pages and SleekAI explains USCIS, court, academic, and corporate certification differences correctly. USCIS specifically requires a Certificate of Translation Accuracy in a specific format and does not require notarisation. Court filings often require a sworn translator's affidavit and may require notarisation. Academic credential evaluations need WES or ECE-compatible formatting. The bot distinguishes them based on the prospect's stated use case.

Yes. Add surcharge rules as pricing pages or options, and SleekAI applies them correctly when prospects mention deadlines or notarisation needs. The bot only adds notarisation when the filing actually requires it, since USCIS does not need it but a state court often does. Rush turnaround triggers a confirmation that a specialist in that language pair is available before the bot commits to the deadline in the quote.

SleekAI doesn't connect directly to memoQ, Trados, Smartcat, or Phrase out of the box. It logs the project intake in WordPress and you push the summary into your TMS through a webhook or a manual handoff. Most translators use a small Zapier or Make.com flow to forward intake summaries from the SleekAI webhook into their project management tool, which avoids the heavy custom integration work.

Yes. GPT-4o and Claude both handle most major languages natively, including legal and medical vocabulary in Spanish, Mandarin, Russian, Portuguese, Arabic, French, and German. Many translators run a single bilingual or multilingual bot rather than one bot per language. Prospects often start in their source language and switch to English mid-conversation, and the bot handles the switch seamlessly without separate configuration.

The system prompt instructs Lingo to capture project metadata - language pair, word count, deadline, certification - not document content. Actual files are uploaded to your secure portal after intake, never pasted into chat. This matters for legal contracts, medical records, and corporate documents where the client expects NDA-grade handling. The bot can be told explicitly to refuse if a prospect tries to paste a confidential document into the chat window.

Yes, when you have a localisation page. Website localisation has different inputs from document translation: word count comes from a crawl, file format is usually XLIFF or CSV, and the project may need translation memory leveraging or an SEO factor. The bot captures URL, languages, scope, and CMS, then quotes from your localisation rate table or routes to a project manager for a custom estimate when the project is too large for an automated quote.

Yes, when you offer apostille service. Apostille is a separate filing with the Secretary of State and has its own fee, turnaround, and document requirements that differ from notarisation. The bot quotes apostille only when the prospect's stated use case requires it (Hague Convention foreign filing) rather than adding it by default, and the price comes from your apostille service page so updates flow through automatically.