You might trial a conversation platform in a day, then discover that your project's hardest part never appeared in the demonstration: changing an appointment in an existing system, verifying the requester or transferring the conversation to an employee authorized to decide. A convincing automatic answer is therefore insufficient grounds for selecting a platform.
A different requirement does not mean rebuilding everything from scratch. A platform may cover conversations and channels while one workflow needs custom integration. The useful decision is to identify that gap, its size and its operational owner, then compare alternatives delivering the same journey.
Test three cases before asking the price
Consider a fictional training company receiving course questions and booking changes. The first case asks about course content; the second asks for a learner's booking time; the third requests a change requiring employee approval. We assume neither that a bot may make the change nor that private information is available without verification.
Give the vendor test data and an approved answer source for each case, then request a step-by-step explanation. Is it answering from static content, reading another system or changing that system? Separating these types avoids comparing a general-answer platform with a solution expected to perform operational work.
A gap worksheet for the demonstration
| Case | Proposed implementation category | Evidence required |
|---|---|---|
| Approved general answer | Content or knowledge configuration within available limits. | A correct answer and an update visible after approved publication. |
| Private appointment lookup | Available connector or integration requiring development. | Access verification and retrieval of the user's own record. |
| Change requiring approval | Employee workflow or custom action with permissions. | A documented request, approval and understandable outcome. |
| Missing knowledge or failed connection | A fallback or accepted manual follow-up. | Acknowledgement of limits and handoff without invented success. |
Beside each row, record the product, component, additional work and exclusions. “Supported” should not mean “could be programmed later”. If a connector is demonstrated, ask which actual operations and permissions it covers and what must change in the source system.
Test the channel people will use
A successful conversation inside a platform editor does not establish identical behavior on a website or the required messaging channel. Request the journey on its intended channel and review language, messages, links, verification and handoff. Channel terms and accounts must be checked during implementation; this article promises no channel availability for every business.
Microsoft Copilot Studio documentation distinguishes changing an agent from publishing it to connected channels. Its handoff documentation explains that transferring context to an employee depends on configuring a suitable service platform connection. Another escalation path may provide only a message or link. The proposal should therefore define “handoff” in the solution you are buying.
Who can change content after launch?
Ask an authorized team member to amend, review and publish test information, then verify that the intended version appears. Ask how testing is separated from live use and how an unsuitable change is reversed. These are product management questions, beyond the quality of one answer.
Specify deliverables: content, conversation flows, integration definitions, available operating settings and documentation. Platform terms may allow some elements to be exported and others not. Request an understandable sample export rather than a general statement that you own everything. Owning your content does not mean owning the platform software.
When does each approach make sense?
Platform configuration may be preferable when demonstrated capabilities cover the important cases and your team can operate within acceptable limits. Custom integration may fit when the gap concerns one process and suitable interfaces exist. If core business rules, access boundaries and channel experience need extensive work, request deeper development discovery rather than hoping a subscription will suffice.
Custom development does not imply zero subscriptions or an end to maintenance. For each alternative, ask about updates, failure monitoring, changing third-party interfaces and knowledge management. Compare operational and exit responsibilities alongside construction time, then test the most important failure case before deciding.
The WhatsApp chatbot cost worksheet separates spending components, while knowledge readiness helps prepare sources. When requesting a conversation solution from Nextwave, send the three cases and gap worksheet to discuss an alternative whose suitability can be demonstrated.
Comparison references and limits
Microsoft's publication and channels and live employee handoff documents were opened on 3 November 2026. They support the stated distinctions in that product, not equivalence between platforms or a product recommendation. The example and comparison tool are editorial proposals.
