Togile

A conventional record system with rule based automation and no model layer described anywhere.

Two passes across seven independent directory listings and the verified review base located no generative capability, no assistant, no forecasting model, no conversational interface and no reference to artificial intelligence in the product description at all. In a sweep where nearly every vendor leads with an agent, that silence is notable.

One feature edges toward it. Lead management is described as ensuring leads are accurately scored, properly segmented and nurtured with personalised communication, but nothing indicates whether scoring is a configured rule set or an inferred model, and given the rest of the product the former is the likelier reading.

What the platform actually automates is deterministic and useful: lead capture, automatic assignment by defined criteria, task creation, follow up reminders, scheduled email sequences and workflow branching, all configurable without writing code.

The no code configuration is the more relevant capability for this buyer, since a smaller team needs to change a pipeline without engaging a developer.

Ask whether lead scoring is rule based or model driven.

The alerting set includes two categories most record systems at this level do not carry.

The ordinary ones are there: event triggered notifications for new leads and meetings, customer interaction alerts when someone engages with an email or form, and lead activity alerts when a prospect takes a meaningful action.

The two that matter more are service level breach alerts and system failure alerts. The first notifies when a service commitment is breached or approaching its deadline, which turns an obligation into something visible while it can still be met rather than reported afterwards. The second notifies on system errors or failures for quick resolution, which is an operational transparency choice: most vendors would rather a customer did not know.

Around them sit real access controls described by a customer in financial services: profile based access governing what each user can reach, network address restriction limiting where the system can be used from, and number masking concealing customer telephone numbers from individual agents.

Automation covers lead assignment, task creation and workflow branching without code.

What two passes could not locate: any audit trail, any approval workflow and any change history.

Ask whether an audit trail records who changed what.

Lead scoring is referenced and nothing describes what performs it.

The only capability approaching this axis is a statement that lead management ensures leads are accurately scored and properly segmented. Two passes across every reachable listing located no model provider, no method, no inputs, no accuracy figure and no indication whether scoring is inferred or configured from rules the customer sets.

Given the rest of the product is explicitly rule based and no code, a configured scoring model is the more likely reading, and if so there is nothing to disclose and the grade simply reflects an empty surface.

The distinction matters to a buyer for one practical reason. A rule based score is inspectable and adjustable by the person who set it. An inferred score is neither, and it determines which leads a representative works and which are quietly left. A buyer should establish which they are getting before relying on the ranking.

Nothing else in the product generates content, drafts messages or makes predictions, so no other disclosure obligation arises.

Ask whether scoring rules are visible and editable by an administrator.

Verified reviews across several independent directories, carrying enough specific detail to be credible, and no vendor supplied evidence at all.

The reviews are the substance here and they read as genuine rather than solicited. One reviewer names the competing product they left and why, citing heavy charging and poor service quality. Another itemises the specific processes automated: lead churning, automatic assignment and task creation. A third, working in financial services, names four particular security controls by function rather than repeating marketing language. Another describes smooth onboarding and quick team adoption.

That level of operational specificity is harder to manufacture than a superlative.

One review runs sharply the other way and belongs in the record: a reviewer states they did not like the service, describing the company as money minded and alleging heavy charging through false promises. That sits directly against the fixed price positioning the other reviewers praise, and a buyer should establish which experience is typical.

What two passes could not locate: any named customer, any logo, any case study, any aggregate rating, and any outcome figure. Review volume appears modest across all directories.

Ask for customer references in your own sector and size band.

Number masking is a recipient protective control and it appears nowhere else in this index.

Described by a financial services customer among the platform's security features, masking conceals customer telephone numbers from the individual agents using the system. The agent can place the call without seeing the number. That protects the customer's contacts from being copied, taken to a competitor or misused by staff, and in sectors handling sensitive relationships it is a meaningful safeguard for the person whose number it is rather than for the business holding it.

Around it, leads originate from the customer's own capture rather than a supplied database, so nobody is contacted because they appeared in a purchased list.

What two passes could not locate: any unsubscribe mechanism for the automated email sequences, any do not call screening ahead of the call tracking and interactive voice features, any consent basis, any suppression list and any reference to messaging regulation in the markets served.

The email sequencing capability is the live gap, since a record system sending scheduled nurture sequences needs an exit route for the recipient.

Ask how recipients unsubscribe from automated sequences.

Four access controls described by a customer in a regulated sector, and no vendor documentation to confirm any of them.

The controls are substantive and unusually specific for this tier. Encryption described as covering everything in the system. Network address restriction limiting where the platform can be reached from. Number masking concealing customer telephone numbers from agents. Profile based access governing what each user can see.

Those four together constitute a real posture rather than a claim, and the fact they were itemised by a financial services user explaining why the product suited their obligations carries more weight than a marketing page would.

The difficulty is provenance. All of it reaches this record through a customer review. The vendor's own site was unreachable in this pass, so no privacy policy, processing agreement, subprocessor list, retention schedule, deletion commitment or residency statement is recorded.

Jurisdiction sharpens the question. An Indian company holding customer data for financial services clients operates under specific local requirements, and a buyer outside that market would need to establish where data resides.

Ask for the privacy policy, processing agreement and hosting location.

No data about people is supplied with the product.

Two passes across every reachable listing located no contact database, no record count, no enrichment engine, no lead finder, no intent signals and no third party data supplier anywhere in the feature set. The platform is a place to hold relationships a customer already has, populated by their own capture, their own imports and their own integrations.

That is clean by construction and it removes the provenance question that dominates this axis for most records in this index. Nobody in the system arrived from a pool of unknown origin.

Commerce platform integrations bring purchase records in from the customer's own store, and advertising platform connections bring in leads generated by campaigns the customer ran, both of which are first party sources.

The one unexplained element is what informs lead scoring, described as ensuring leads are accurately scored without stating what the assessment draws on. If it operates only on data the customer captured, the position is entirely clean.

Ask whether scoring uses any data beyond what the customer holds.

Every reported integration is a published partner interface used the way it is meant to be used.

The reported set spans mail, calendar, two social platforms, an advertising network, email marketing services, marketing automation, two commerce platforms and interactive voice systems. Each of those publishes a commercial interface for exactly this purpose, and connecting through them is the sanctioned path rather than a workaround.

Two passes located no scraping, no social network automation of the prohibited kind, no browser extension operating a property the vendor does not own, no account renting and no capability whose viability depends on another platform failing to notice it.

That position follows from what the product is. A record system managing a company's own customers has no reason to reach into somebody else's network, and this one does not.

One reported capability deserves a question rather than a conclusion. Social media management is listed as operating inside the record system, allowing accounts to be managed and engagement tracked there, and nothing describes whether that runs through official interfaces or otherwise.

Ask how the social media management feature connects to those platforms.

Almost no model surface to be unsafe, and a stewardship position described entirely by a customer rather than the vendor.

On safety there is little to assess. Nothing generates content, holds conversations or acts autonomously. Lead scoring is the only inferential capability referenced and its method is unstated, so the exposure is limited to a ranking a representative can presumably override.

Stewardship is where the substance sits, and it is genuinely reasonable for this tier: encryption throughout, network address restriction, number masking, and profile based access control. Those are the controls a financial services buyer would test for, and a customer in that sector says they were satisfied.

The problem is that this record cannot confirm any of it. Every detail arrives through a review rather than through vendor documentation, and the direction of that flow is the wrong way round for assurance purposes. A buyer needs the vendor to state these controls, not a third party to have found them adequate.

Two passes located no security page, no certification, no encryption specification, no incident response process, no breach notification commitment, no named security contact and no vulnerability disclosure route.

Ask the vendor to document the security controls in writing.

Nothing here creates a false impression, and one control protects the recipient rather than the customer.

Two passes located no persona, no synthetic sender, no cloned voice, no generated content presented as personally written, no automated social action manufacturing the appearance of interest and no rented identity. Communication runs from the customer's own mail, their own numbers and their own representatives, to people the customer already holds a relationship or an enquiry from.

Number masking is the feature worth drawing out. By concealing a customer's telephone number from the individual agent handling them, it protects that person's contact detail from being copied or taken elsewhere. Across this index almost every control protects the business or the sender; this one protects the person on the other end.

Two gaps remain on the outbound side. Automated email sequences run with no unsubscribe mechanism described. And call tracking operates with no recording notification described, in a market with its own consent expectations.

Ask what a called party is told when a call is tracked or recorded.

A broad reported integration set, including one category unusual at this level.

That category is interactive voice response. Connecting a record system to inbound call routing means a caller reaching the phone tree is matched to their record before an agent picks up, which is a genuine capability and one most record systems at this price point do not offer. Combined with call tracking and number masking, it suggests a product built with telephone heavy operations in mind.

The rest spans mail, calendar, two social platforms, an advertising network, email marketing services, marketing automation, and two commerce platforms for unifying purchase history with customer records.

An interface is reported available and described as customisable for integrating with other business applications or extending the platform. Bulk data import and export is listed explicitly as a capability rather than left implied.

The deduction is entirely about verification. All of this reaches the record through directory listings, and two passes located no integration directory, no interface documentation, no authentication scheme and no webhook description on any reachable surface.

Ask whether interface documentation is published and which systems are supported natively.

The client side is documented in detail and the server side is entirely unstated.

What directories report: a cloud hosted service running in a web application, accessible through mobile browsers, with desktop platform support listed for both major operating systems. Support is offered by email, telephone, live chat, training and a ticketing system, which is a fuller set than most vendors at this tier provide.

Network address restriction is the one infrastructure adjacent control described, and it implies the platform can enforce access rules by source network, which matters for a customer wanting the system reachable only from their offices.

What two passes could not locate: any hosting provider, region, data centre, residency commitment, tenancy or isolation model, encryption specification, backup position, continuity plan, uptime commitment or status page. The vendor's own site was unreachable in this pass, which is where most of that would live.

Residency is the live question given the operating company is Indian and reviewers include financial services users whose own obligations govern where customer data may sit.

Ask where data is hosted and whether regional options exist.

Real controls, described by a customer, with nothing published to stand behind them.

The controls themselves are credited elsewhere in this record and they are reasonable: encryption, network address restriction, number masking and profile based access. The problem on this axis is the direction the information travelled. A reviewer in financial services found those controls and found them adequate. The vendor has published nothing this pass could reach.

Two passes located no certification of any kind, no audit report, no examination, no penetration test, no trust portal, no dedicated security page, no encryption specification, no subprocessor list, no vulnerability disclosure route, no named security contact and no status page.

That gap has practical consequence for exactly the buyer this product seems to attract. A financial services firm adopting a record system will be required by its own supervisors to evidence its supplier's controls, and a customer testimonial is not evidence a compliance function can file.

The vendor's own site was unreachable in this pass and may carry material this record could not see.

Ask whether any independent security assessment exists and request it in writing.

Unlimited users at a fixed price is the position customers name, and one review alleges the opposite experience.

The positive framing is consistent across several independent reviewers and is specific rather than vague. One describes the value as growing the team without any anxiety about upgrading plans for extra users. Another repeats it in almost the same terms. In a category that meters by seat almost universally, removing headcount from the pricing equation is a genuine structural choice and it is plainly why several customers chose the product.

A lifetime free plan and a free trial are reported, with both monthly and yearly payment options available.

Against that sits one review stating plainly that the reviewer disliked the service, describing the company as money minded and alleging heavy charging through false promises. That directly contradicts the fixed price framing and cannot be reconciled from outside.

And no figure surfaced anywhere. Across seven directory listings, two passes located no price for any tier, in any currency, with several listings routing to a quote request instead.

So the model is legible and the number is not.

Ask for the fixed price in writing, and what is excluded from it.

Bulk export is listed as a capability rather than left to be discovered.

Directory listings state that customer and business data can be imported and exported in bulk or through integration with other systems. For a record system that is the answer this axis asks for, and several vendors built earlier in this session could not supply it: one reserved interface access for its highest tier, another described no export mechanism at any price.

A customisable interface is additionally reported, described as available for integrating with other business applications or extending the platform, which gives a second programmatic route.

Commerce and marketing integrations mean some customer data already lives in systems the customer owns independently.

What two passes could not locate: any export format, any scope statement covering whether communication history and custom configuration travel, any deletion commitment, any retention position after cancellation and any account closure process.

The configuration question matters here more than usual, because the product's selling point is heavy customisation of fields, form layouts, reports and dashboards, and that work is the customer's own and may not be portable.

Ask whether custom fields, layouts and reports export with the data.

Automated email sequences with no sending discipline described anywhere.

The platform runs scheduled email sequences, automated nurture communication and follow up reminders. Two passes across every reachable listing located no warm up capability, no sender authentication guidance, no domain or inbox rotation, no address verification, no bounce handling, no placement testing, no sending limits and no reputation monitoring.

One mitigating factor is structural rather than stated. Directories report integrations with established email marketing services, which suggests some customers send through a specialist platform that supplies those controls rather than through the record system directly. If so the discipline exists, just not here, and a buyer should establish which path their sending takes.

The risk profile is also lower than for a dedicated outbound tool. Sequences run to leads the customer captured themselves rather than to cold purchased lists, and complaint rates on that traffic are lower.

The telephone side carries a parallel gap, with call tracking and interactive voice features and no caller reputation monitoring described.

Ask whether sequences send from the platform directly or through a connected email service.

The stated segmentation covers everybody, and the evident one is narrower and more informative.

Directory listings report the product serving freelancers, startups, small and medium enterprises, agencies and enterprises across all industries. Claiming every size and every sector is not segmentation, and a buyer learns nothing from it.

What the evidence actually shows is more useful. The operating company is Indian and Bangalore based. The competitive frame in reviews is other Indian mid market record systems, with one reviewer naming the local product they left. The unlimited user pricing addresses a market where per seat costs bite hardest. Reviewers include financial services users, and the security controls they describe, particularly number masking and network address restriction, are the ones telephone heavy Indian operations ask for.

Interactive voice integration points the same way.

The platform is available in English only, which bounds the addressable market despite the all industries claim.

Ask which markets outside India the platform is sold and supported in.