Short answer: start a Node.js ticket-summarization SaaS with chat completions, put the provider behind one tiny adapter, and choose the vendor only after checking model availability, context limits, US/EU requirements, and batch support.
Embeddings don't improve the first version of this job. They become relevant later if the product adds search or an ask-your-docs flow. For short-to-medium tickets, a prompt plus a chat model is the smaller system and the easier contract to replace.
Keep it boring.
Rollout phase zero: freeze the application-owned summary contract
The decision is less about which model writes the prettiest demo summary and more about what the application owns. A healthtech support pipeline has an input ticket, a stable summary instruction, and an output string. If those three things live behind an application interface, moving between an OpenAI-compatible gateway and a direct provider is contained. If provider response objects leak into queues, database records, and UI components, the migration gets wide fast.
