Install with Claude
Explain where the shared layout lives, then ask Claude to insert your project snippet there once.
Use the installation prompt ↘Claude, ChatGPT, Gemini or Grok.
Same request. Same little snippet.
Give your AI the code from your Orka project. Ask it to put the widget in your site’s shared head. Then send your first test message.
Get the prompt ↓Explain where the shared layout lives, then ask Claude to insert your project snippet there once.
Use the installation prompt ↘Share the relevant layout or give your coding workspace access, then ask ChatGPT to make the same change.
Use the installation prompt ↘Provide the project context and snippet, then ask Gemini to show the changed files and how to test the result.
Use the installation prompt ↘Give Grok the code it needs and ask for a precise change. Apply the proposed patch if your setup cannot edit files directly.
Use the installation prompt ↘Go to your Orka dashboard, select the project and open Settings → Installation. Click Copy Code under How to embed. If your site is new, create its project first.
Paste it with the prompt below. Name your framework or builder. In a coding workspace, let the assistant edit the shared layout. In a chat-only tool, ask it for the exact change and apply that change in your editor.
Open your public site, send a message, check it reaches the correct project in Orka and reply. Visit another page to confirm the widget is loaded only once and stays available.
The request is intentionally the same across assistants. What matters is access to your project and the correct installation snippet, not a special integration.
Add Orka live chat to this website using the exact installation snippet below.
1. Find the shared HTML head or the appropriate script-loading component for this framework.
2. Add the snippet once, preserving its project ID and the widget.orka.chat script address. Avoid duplicate loading during client-side navigation.
3. Preserve the existing layout, scripts and consent settings. Do not add an API key or invent an SDK.
4. Show the files changed and explain how to test the published site on desktop and mobile.
5. If you cannot edit this project directly, give me an exact patch and tell me where to apply it. Do not claim it is installed until it has actually been added.
Here is my complete Orka project snippet:
[PASTE YOUR OWN SNIPPET FROM ORKA → SETTINGS → YOUR PROJECT → INSTALLATION HERE]The example below masks the project ID. Replace it with the complete code you copied from your own Installation screen. It loads the public widget; it does not contain a provider secret.
<script type="text/javascript">window.ORKA_APP_ID="YOUR_PROJECT_ID";(function(){d=document;s=d.createElement("script");s.src="//widget.orka.chat/app.js";s.async=1;d.getElementsByTagName("head")[0].appendChild(s);})();</script>Adding a support widget with an assistant is different from letting AI answer visitors. You can use Orka entirely for human conversation, ask Orky for drafts, or configure automatic replies from your knowledge.
One project can be an experiment you launched last night. Another can be the SaaS that pays the rent. They can share the inbox without sharing their identity.
Support for your vibe-coded projects ↗Your assistant can explain the steps, but the final edit may belong in your builder’s Header or Custom Code settings. Follow the guide for your platform and its plan requirements.
WordPress, Shopify, Webflow, Framer and more ↗Ask for the framework’s normal client-side script loader. Do not run browser globals such as window or document during a server render. Test internal navigation to avoid adding a second copy.
Still wondering about something?
Ask a human at Orka ↗
Yes. Give it your complete project snippet and enough access or code context to change the shared layout. If the assistant cannot edit or deploy the project, it can return a patch for you to apply. The final check is a test conversation on the published website.
No provider API key is required to add the chat widget. You use your existing coding assistant to edit your site. Connecting an AI provider for Orky’s drafts or automatic replies is a separate setup inside Orka.
Open the Orka dashboard, select the relevant project, then Settings → Installation → How to embed → Copy Code. Each product should use its own project snippet so your inbox knows where messages came from.
Yes, if you can edit its shared layout or custom-code settings. Tell the assistant which framework or website builder you use. Ask it to add the loader once and test internal navigation as well as the first page load.
No. YOUR_PROJECT_ID is deliberately a placeholder. Use the full snippet from your own Orka project. Never copy another customer’s project ID.
Ask for the exact file change, then apply it yourself or through an editor with repository access. For hosted builders, use the platform’s Custom Code or Header settings. An answer in a chat window alone does not publish a change.
No. Widget installation makes chat available. Set up your knowledge, provider and AI behavior separately. Start with drafts if you want to review answers before letting Orky reply automatically.
Written by Orka. Valid as of September 2026. Platform requirements can change. Corrections are welcome at [email protected].
Unlimited projects. A free help center.
A human when it matters, Orky when you need a hand.