Rasayel

Model capability sits inside a flow builder rather than underneath the product. The chatbot is a no code drag and drop canvas of deterministic nodes, with model driven nodes available among them for identifying high potential leads, filtering poor fit ones, and answering from a knowledge base trained on the customer's own documents. A conversational teammate is announced but gated behind an early access request, so it is not yet part of what a buyer gets.

Apply the removal test and the platform stands complete: shared team inbox, assignment and routing, private notes, broadcasts to segmented lists, template management, structured forms, workflow automation, reporting, mobile application, systems of record integration and two programmatic interfaces all survive. What is lost is qualification scoring and automated answering.

Handover to a person is the designed outcome rather than a fallback, and the routing logic is described rather than gestured at: a qualified conversation is assigned automatically on three named criteria, being the contact's language preference, the use case, and agent availability, which also balances workload across the team.

Around it sit roles and permissions, assignment, private team notes that stay internal to the conversation, personalised notifications and an organised inbox, so a supervisor can see who owns what. Holding it off the top band, no approval step sits between a bot message and the recipient, no audit record is described anywhere, no ceiling governs broadcast volume, and the autonomous teammate now in early access arrives with no published governance material of any kind.

Four model capabilities are marketed, covering lead scoring, poor fit filtering, knowledge base answering and a forthcoming conversational teammate, and no provider, model, family, version or hosting arrangement is named for any of them.

One disclosure of substance exists and it concerns inputs rather than models: the knowledge base is stated to be trained on the customer's own frequently asked questions, product guides and support protocols, so a buyer knows what the answering behaviour is grounded in even though they cannot know what generates it.

One testimonial carries a full name, an exact job title and a named employer, and links through to the underlying written account rather than standing alone. Two published customer stories carry specific figures with the customer identified: forty percent workload reduction and doubled sales at a named accommodation business, and sixty eight percent time saved with fifteen percent sales growth at a software company whose story opens by describing its numbers being banned before it arrived, which is a candid framing few vendors would publish.

Two third party review platforms are linked directly rather than quoted selectively. Holding it off the top band, the trusted by row renders as twenty empty placeholders to a fetcher so the customer roster is unreadable, the two headline figures on the campaigns page are channel statistics about the messaging service rather than results the vendor produced, and one of the three homepage testimonials is from the vendor's own sales team. That is labelled honestly, and it is also the one carrying the claim about closing thirty percent of deals.

The compliance apparatus here is largely inherited rather than authored, and it is real. Everything runs through the messaging service's official business interface, where the platform owner requires the recipient to have opted in before a business may initiate contact, requires message templates to be pre approved before a broadcast, enforces a quality rating that throttles a sender who generates complaints, and restricts free form messaging to a window the customer opened.

Those are consent and suppression controls enforced by a third party rather than promised by the vendor, which makes them harder to quietly relax. The vendor's own published education covers opt in, segmentation, template compliance and list quality directly.

Holding it off the top band, the vendor takes no position of its own on any statute, no consent standard appears in its product material, no suppression or opt out mechanic is described on the pages read, and the campaigns page sells bulk messaging to thousands.

A privacy policy and terms of service exist on the documentation subdomain and neither was opened, so this row is graded on the surrounding surface and flagged. One published claim needs disentangling rather than crediting. The site advertises the channel as secure and encrypted, which is true of the messaging service's own transport, and the product being sold is a shared inbox where an entire sales team reads, searches and reports on the content of those conversations, so the vendor necessarily holds them in readable form.

The marketing does not draw that distinction anywhere. No retention period, processing addendum, sub processor list or residency statement appears on the pages read, at a platform holding the complete conversation history of a business with its customers plus synchronised records from two systems of record.

The vendor sells no contact data and compiles no third party records, so the baseline is clean. Records arrive by import from the customer's own system of record, and conversations begin either from the customer's own list or from the contact themselves through a chat widget, a link or a scannable code, all of which are first party routes.

Graded in the middle rather than higher because the clean position follows from the business model rather than from any published provenance policy, and no statement addresses what the vendor may do with conversation content beyond delivering the service.

The cleanest conformance position graded in this index, and it is verified rather than merely asserted. The vendor is a formally recognised partner of the platform it builds on under two named partner programmes, which is a status conferred by that platform after review rather than a claim the vendor makes about itself.

Everything runs through the official business interface: numbers are registered to the customer with the platform owner through the sanctioned process, templates go through pre approval, and free form messaging is confined to the window the platform defines.

Six of the site's frequently asked questions are about doing exactly this correctly, covering what the business interface is, how to register a number, how long registration takes, and how to migrate a number legitimately off the consumer application. Nothing rents an identity, rotates an account, ships an extension or works around a limit, and the channel identity belongs to the customer rather than the vendor.

The one tension worth recording is tonal rather than structural: the campaigns page markets bulk messaging to thousands, which is within the rules only because template approval stands between the customer and the send.

Nothing published addresses retention, training, cross customer boundaries or where inference runs for any of the model features, and a conversational teammate is being offered in early access with no governance material at all. The one identified input is the knowledge base, trained on the customer's own documents, which is the right corpus and says nothing about whether anything learned from one customer's conversations reaches another. The material at stake is the full text of a business's conversations with its customers, held in a shared inbox and searchable by an entire team.

A chatbot converses with inbound contacts, asks qualifying questions, collects an email address and decides whether the person is worth a human's time, and nothing on the pages read states whether the person is told they are talking to software, or how they reach a person if they want one. Three mitigations are real and structural rather than promised.

The messaging service requires the recipient to have opted in before a business can initiate contact, so nobody is approached cold on this channel. Handover to a named human is the designed path with routing rules behind it. And the business account displays a verified business name to the recipient by construction, so the sender is never disguised. No position is taken on the European marking obligation.

Two systems of record are live with dedicated integration pages and real time conversation logging into one of them described in a customer story, a third is named as forthcoming, and an automation platform connector is published. Both a graph interface and a representational interface are documented on a developer subdomain of their own, alongside a public status page, a documentation site and a mobile application.

Three free entry point tools are published, covering a chat widget, a link generator and a scannable code generator, which is genuine breadth at the top of the funnel. Holding it off the top band: no marketplace exists, no webhook documentation was surfaced on the pages read, federated sign on appears nowhere, and the third system of record has carried a forthcoming label on a site whose copyright line still reads two years old.

Hosting provider, country, region, data centre and residency option are absent from every page read, and no security page or trust centre exists where such a statement would sit. The operating company is named in the copyright line and no corporate address is published anywhere on the site.

Two facts establish that the question matters rather than answering it: the interface is published in three languages including Arabic and Brazilian Portuguese, indicating service across at least three distinct regulatory regions, and the platform holds conversation content belonging to businesses in each of them.

A public status page runs on its own subdomain and a documentation site sits alongside it, which is more operational transparency than most vendors of this size publish. Transport encryption on the messaging channel is provided by the platform owner rather than by the vendor.

Past those, no certification, audit report, attestation, penetration test, control set, encryption statement covering data at rest, trust centre or vulnerability disclosure route was located on any page read, and the terms and privacy documents were not opened. Partner status with the platform owner implies a review process rather than a security certification and should not be read as one.

A pricing page sits in the navigation and the plan comparison on the homepage does not render to a fetcher, showing a popular badge and an invitation to schedule a call where the figures should be. Four commercial terms are published unambiguously and they matter: a seven day free trial, no card required, free migration and free support. What no page read supplies is any figure at all, whether a seat rate, a tier, a message allowance or a conversation charge.

The gap is wider here than the missing number suggests, because the underlying messaging service bills the customer per conversation on its own schedule, so a buyer faces two stacked cost layers and can see neither on this site.

Free migration appears on the homepage as a headline benefit and it points inward only. No export function, file format, post termination right, deletion timeline or retention period is described on any page read, at a platform holding the complete conversation history of a business with its customers. Two structural facts run the customer's way and are the reason this sits in the middle rather than lower.

The messaging number is registered to the customer with the platform owner rather than to the vendor, so the channel identity itself is portable and can be moved to another provider. And conversations synchronise into the customer's own system of record in real time, so a substantial part of the record already lives somewhere the customer governs.

The channel is business messaging rather than email and the discipline is mostly enforced by the platform owner, which is a stronger arrangement than a vendor policing itself. Templates must be pre approved before any broadcast, a quality rating governs how much a sender may send and falls when recipients complain, and free form messaging is confined to a window the recipient opened.

The vendor surfaces template approval status inside the product so a customer can see where they stand, and publishes education on segmentation, list quality and compliant bulk sending. Its own customer story about a business whose numbers were banned before switching is an unusually direct acknowledgement of what happens when this goes wrong.

Holding it off the top band, the vendor publishes no discipline of its own: no per account cap, pacing rule, ramp schedule, quality rating threshold or stated response when a rating degrades. The campaigns page leads with a ninety eight percent open rate and bulk messaging to thousands, which is volume framing rather than restraint.

Unusually specific and self limiting for a vendor this size. The buyer is stated as business to business sales teams, and a floor is published twice: the guide on the homepage says it suits sales teams of ten or more people. That is a boundary statement functioning as a qualification gate, which is rarer than a persona list. Interfaces are published in three languages covering English, Arabic and Brazilian Portuguese, which is real geographic reach stated as a product fact.

Named customers span human resources software and travel accommodation. A partners page and a reseller programme extend the picture. Holding it off the top band: no customer count, no country or region list, no industry coverage data, and no statement of who should not buy beyond the team size floor.