Straight answers, including the awkward ones

There is no hard floor, but the honest answer is that the value scales with how much routine traffic you carry. If one person comfortably answers every inquiry within the hour and nothing is being dropped, you do not have the problem Fashti solves yet.

The clearest signal is not door count. It is whether inquiries, resident messages or maintenance requests regularly wait longer than you would like, and whether anyone is doing operational work in the evening.

The platform is built for residential operations, and that is where it is strong. Commercial leasing has a different rhythm: fewer, larger, more negotiated transactions, where the routine middle we automate is a much smaller share of the work. We would rather say that plainly than take the engagement.

Yes, and most teams do at first. Leasing alone is a common starting point. The pillars share the same portfolio model, so adding a second later is configuration rather than a new implementation, and the two improve each other once both are running.

A website chatbot answers questions. Fashti completes work. The difference shows up in whether the conversation ends with information or with a viewing in your calendar, a lead updated in your CRM, a work order raised against a unit and a document sent for signature.

The second difference is context. A chatbot usually works from a knowledge base someone wrote. Fashti works from live portfolio data, which is why it can tell a renter the actual availability date rather than inviting them to get in touch.

No. Fashti is specifically designed not to be one. Your property management system stays the financial system of record and your team keeps working in it. If you are actually in the market to replace it, we are not the product you want.

We tell you during assessment, before any agreement. Partial connection is often enough: a system Fashti can read but not write to still removes most of the work, with the write routed to a person as a clear task. Where the gap makes your goal unachievable, we say so rather than proceeding.

The full picture is on the integrations page.

No. We use commercial model providers under terms that exclude training on customer content, and we do not train or fine tune on your operational data for anyone else's benefit. We also do not pool your data into a benchmarking product or sell it. The detail is set out under what language models are allowed to see.

Yes, in a structured format, on request or on a schedule. Most of what Fashti produces is already in your own systems because that is where it writes, and the conversation histories and audit trail are exportable on top of that.

The policy engine, which checks every outbound action against the rules you configured before it happens. Anything above a spending threshold, outside your standard terms, touching a notice, or simply unfamiliar is held for a person instead of being attempted.

Behind that sits the audit trail, so when you ask why something was sent you get a specific answer rather than an explanation of how the technology works.

Qualification runs on the criteria you define, applied identically to every applicant, with every question and answer logged. Protected characteristics are not used as criteria and questions touching them are not asked. Conversations drifting towards a topic that should not influence a tenancy decision are escalated rather than handled automatically.

Fashti is a tool, not a compliance guarantee. The obligation remains yours. What the platform adds is consistency and a complete record of how each decision was reached, which is what you need if you are ever asked to demonstrate it.

It will, occasionally, as any operation does. The relevant questions are how quickly it is visible, how far it could propagate, and whether it can be undone. Thresholds limit the blast radius, the audit trail makes the error findable, and the workflow can be narrowed or paused immediately while the rule behind it is fixed.

We also report the escalation rate alongside the automation rate, so a workflow drifting towards trouble shows up as a trend rather than as an incident.

Yes, and during onboarding you should. The shadow period runs Fashti in draft only, so you compare what it would have sent against what your team actually sent. Some customers keep certain workflows in review mode permanently, which is a legitimate configuration rather than a failure to progress.