Claude 4.5 vs GPT-5 for Customer Support in 2026: How to Test Them
Anthropic and OpenAI are retiring Claude Sonnet 4.5 and GPT-5 from their APIs. Compare them on policy, tone, tools and cost, then test a successor.
- Updated
- Reading time
- 11 min read
16 sections
Claude 4.5
vs
GPT-5
TL;DR:
- Test both models on the same support conversations. General model rankings do not tell you whether either model will follow your refund policy.
- Score tone, policy adherence, tool arguments, escalation behavior, and cost per completed conversation.
- Start with one model. Add a second only if it produces a measured gain that justifies the extra routing and monitoring.
- Recheck vendor pricing before you decide. Token rates and caching terms change.
- Both models are scheduled to leave their vendors' APIs: Claude Sonnet 4.5 on November 30, 2026 and GPT-5 on December 11, 2026. Rerun the same tests on their successors.
Neither Claude Sonnet 4.5 nor GPT-5 is the better support model in every case, and both are now on their way out. As of November 12, 2026, Anthropic lists Claude Sonnet 4.5 as deprecated with a Claude API retirement date of November 30, 2026, and OpenAI lists GPT-5 for removal from its API on December 11, 2026. If you are choosing between them today, the useful output is a test method you can rerun on their successors.
What matters for support is narrow: does the model follow your policy, keep your tone, refuse cleanly, and call your tools with correct arguments? Academic benchmarks such as MMLU or GPQA do not answer those questions. Your own conversations do.
This article is desk research from official Anthropic and OpenAI documentation checked on November 12, 2026, plus Chatsy's own model catalog. Chatsy publishes this article and offers both model families inside its product. We did not run a published head-to-head benchmark, so this page gives you test criteria, not a winner.
The models and their status
Claude Sonnet 4.5 (Anthropic): A general-purpose model with tool use and image input. Anthropic's model deprecations page marks claude-sonnet-4-5-20250929 as deprecated on September 30, 2026, retiring on November 30, 2026, with Claude Sonnet 5.5 as the recommended replacement. Anthropic's context window docs list a 200k-token window for Sonnet 4.5.
GPT-5 (OpenAI): A reasoning model with tool use and text and image input. OpenAI's GPT-5 model page lists a 400,000-token context window with a 272,000-token input limit and marks the model as deprecated. OpenAI's deprecations page gives December 11, 2026 as the API removal date for gpt-5 and gpt-5-mini.
Smaller variants: Claude Haiku 4.5 is still listed as active, but its tentative retirement date ("not sooner than October 15, 2026") has already passed, so check the page again before you build on it. GPT-5 mini is on the same removal schedule as GPT-5. Lower-cost models can suit routing, tagging and short factual replies, so include one in every evaluation instead of assuming you need the flagship.
API prices, checked November 12, 2026
| Model | Input per 1M tokens | Cached input per 1M | Output per 1M | Source |
|---|---|---|---|---|
| Claude Sonnet 4.5 | $3.00 | $0.30 (cache hit) | $15.00 | Anthropic pricing |
| Claude Haiku 4.5 | $1.00 | $0.10 (cache hit) | $5.00 | Anthropic pricing |
| GPT-5 | $1.25 | $0.125 | $10.00 | OpenAI pricing |
| GPT-5 mini | $0.25 | $0.025 | $2.00 | OpenAI pricing |
Standard-tier prices only. Anthropic also charges for cache writes ($3.75 per 1M tokens for a 5-minute write on Sonnet 4.5), and both vendors offer batch and other tiers.
Per-token price is only one input. Record input, output and cached tokens for a representative set of conversations. Add retries and tool-call turns. Then divide the bill by the number of conversations that passed review. That gives you a cost per acceptable conversation for your own workload.
If you use these models inside Chatsy
Chatsy does not bill tokens. Each AI response uses a fixed number of credits set by the model in Chatsy's catalog, and credits per response range from 1 to 30 across the catalog depending on the model and plan.
| Model in Chatsy | Credits per response | Lowest plan |
|---|---|---|
| Claude Sonnet 4.5 | 3 | Hobby |
| GPT-5 | 2 | Hobby |
| Claude Haiku 4.5 | 2 | Hobby |
| GPT-5 Mini | 1 | Hobby |
| Claude Sonnet 5.5 | 2 | Hobby |
| GPT-6.1 Sol | 2 | Hobby |
| Claude Haiku 5.5 or GPT-6 Luna | 1 | Free |
Chatsy blocks a reply that would bring usage to the monthly allowance, so the counts below are one short of a clean division:
- Hobby ($40 per month, 500 credits): at most 166 replies on Claude Sonnet 4.5 (166 × 3 = 498) or 249 replies on GPT-5 (249 × 2 = 498).
- Standard ($150 per month, 4,000 credits): at most 1,333 replies on Claude Sonnet 4.5 (1,333 × 3 = 3,999) or 1,999 replies on GPT-5 (1,999 × 2 = 3,998).
These are AI replies, not resolved conversations. A conversation with four AI replies on Claude Sonnet 4.5 uses 12 credits. See how message credits work for the full rules.
Side by side for customer support
| Dimension | What to test |
|---|---|
| Tone control | Blind-review replies against your writing guide |
| Policy adherence | Include exceptions, long conversations and conflicting customer requests |
| Refusal handling | Check whether a refusal explains the next safe step |
| Tool calling | Validate tool choice, required arguments and behavior after an error |
| Image input | Use the screenshots and documents customers actually send |
| Retrieval | Check answers against the source text, not just fluency |
| Cost | Measure the full conversation, including retries and tool turns |
| Latency | Record time to first token and time to a complete usable reply |
Test 1: tone and brand voice
Give both models the same voice guide and the same source material. Hide the model name and ask two reviewers which replies they would send without editing. Count edits, not impressions.
A model's reputation for good prose is not evidence. You will hear that one family follows a brand voice better than the other; treat that as a hypothesis. Your blind review is the only result that counts for your brand.
Test 2: policy adherence
Write a policy with an exception, such as "no refunds after 30 days, except Pro customers, who have 60." Test it on the first turn and again after eight to ten unrelated turns. Then add a customer who pushes for an exception.
Score two things separately: the final decision and the explanation. A model that reaches the right answer for the wrong reason will fail on the next edge case.
Test 3: refusals
A useful refusal explains the limit and offers the next allowed step, such as handing the conversation to a person. Test clear violations, borderline requests, and harmless requests that contain sensitive words. An over-cautious model that refuses "how do I cancel?" costs you as much as one that promises a refund it cannot give.
Test 4: tool calling
Both vendors support function or tool calling, and both have mature SDKs. Ecosystem size matters less than whether the model calls your tools correctly. Build cases where the model should:
- call exactly one tool with all required arguments
- ask for a missing identifier instead of guessing
- call no tool at all
- recover after the tool returns an error or an empty result
In Chatsy, agents can call custom API tools you define (REST methods or an OpenAPI import, HTTPS only, 15-second timeout). Test every tool end to end before you publish it. Connected services such as Stripe or Slack can be set up in the dashboard, but agents cannot run those connector actions yet.
Test 5: images and documents
If customers attach screenshots or PDFs, put real examples in the evaluation. Check whether the model reads the right field, ignores unrelated personal data, and asks for a clearer image when the text is unreadable. An image is evidence for diagnosis, never authorization for a refund or account change.
Test 6: routing and classification
For labels such as billing, technical or sales, start with the cheapest model. Score each label against a reviewed ticket set and include an "unknown" label so the model is not forced to guess. Move up a tier only if the cheaper model misses labels you care about.
When to lean toward each
These are starting hypotheses to test, not results.
Start your test with the Claude model when:
- your policies are long and full of exceptions
- tone is a visible part of the brand (hospitality, premium retail)
- most replies are customer-facing writing that a person will read closely
Start your test with the GPT model when:
- your workflow already runs on OpenAI SDKs and tooling
- you want the lowest token price of the four models priced above for high-volume classification (GPT-5 mini lists $0.25 input and $2.00 output per million tokens)
The "use both" pattern
Some support stacks use a small model for routing and a larger one for the final reply:
- Inbound classification: a small model such as GPT-5 mini or Claude Haiku 4.5.
- Retrieval and tool calls: whichever flagship your code integrates more cleanly.
- Final customer-facing reply: the model that won your blind tone and policy review.
- Internal note or summary: a small model again.
This split adds routing, monitoring and another failure mode. Keep it only if your evaluation shows a clear gain over the best single-model setup. In Chatsy, each agent uses one model that you pick in its settings, so a split like this means separate agents or your own orchestration.
Plan the migration now
Because both models are scheduled to leave their vendors' APIs, run the same test set against the recommended successors before the retirement dates:
- Anthropic recommends Claude Sonnet 5.5 as the replacement for Sonnet 4.5.
- OpenAI's deprecations page recommends
gpt-5.6-solforgpt-5andgpt-5.6-terraforgpt-5-mini, while the GPT-5 model page itself recommends GPT-6 Astra. Check which successors your platform offers. Chatsy's current catalog includes Claude Sonnet 5.5 and GPT-6.1 Sol at 2 credits each on Hobby and above.
Keep your reviewed conversations, scores and costs in one sheet. The next model change then becomes a rerun, not a new project.
When this comparison is not for you
Skip the head-to-head and use your platform's default model if:
- You handle a few hundred conversations a month. Pick what is easiest to integrate and spend the time on your source content.
- You use a hosted AI support product that picks the model for you and does not let you swap it.
- You are prototyping. Ship with one model and evaluate once you have real conversations.
- Budget is the only constraint. Test the smallest models first.
FAQ
Is Claude better than ChatGPT for customer service? Not by default. Run both models on the same reviewed conversations and choose the one that follows your policies with fewer edits.
Is Claude better than GPT-5? It depends on your prompt, tools, source material and review criteria. Neither model is the better choice for every support workflow, and both are scheduled for API retirement, so test their successors too.
Should I switch from GPT to Claude? If your current deployment passes review, do not switch on reputation alone. Run a shadow evaluation and move only if the new model improves a metric you care about.
How many credits do these models use in Chatsy? Claude Sonnet 4.5 uses 3 credits per AI response and GPT-5 uses 2, both from the Hobby plan up. Chatsy's catalog ranges from 1 to 30 credits per response depending on the model and plan.
Bottom line
Do not pick a support model from a leaderboard or a confident blog verdict. Build a small reviewed set of your own conversations, include policy exceptions and tool failures, compare the full conversation cost, and rerun it on each successor model. Keep the simpler setup when the results are close.
If you want to run that comparison without wiring up two APIs, you can change an agent's model in its AI settings in Chatsy and ask the same test questions again in the private playground. Try Chatsy free or see pricing.