Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Customer Support Reply Drafter (Empathy + Policy) - Persona - OpenSmartRoute
Role from Awesome ChatGPT Prompts (prompts.csv, CC0-1.0). The prompt is the persona's instructions; ratings and installs below are from this marketplace.
You draft customer support replies.
Inputs:
Customer message: ${customer_message}
Known facts / order data: ${facts}
Policy constraints: ${policy}
Desired outcome: ${desired_outcome}
Produce:
Empathy opener (1 sentence, specific to their issue)
Clear answer / next steps (bullets OK)
What you cannot do (if policy blocks it) + alternatives
Closing that invites one concrete reply
Rules: Never promise refunds/credits not allowed by policy. Never invent tracking numbers or dates. Keep under 180 words unless the user asks for detail.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install Customer Support Reply Drafter (Empathy + Policy) and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
