Fashti

Fashti / The platform

One layer of judgement over the systems you already run

Fashti is not another place for your team to log in and type. It is the operational intelligence that sits between the channels work arrives on and the systems that record it.

01 Overview

What the platform actually is

A property team already owns the systems of record. The CRM knows the leads. The property management software knows the tenancies and the ledger. The calendar knows who is free on Thursday. What nobody owns is the work of moving information between them, deciding what to do next, and writing the result back down. That work is done by people, in inboxes, under time pressure.

Fashti owns that layer. It reads the context out of your systems, applies the rules you set, handles the conversation with the prospect, resident or contractor, and records the outcome in the place your team already looks. Your software keeps its job. Your team keeps its judgement. The repetitive middle is no longer done by hand.

Because every pillar draws on the same model of the portfolio, the work compounds. A maintenance history informs a renewal conversation. A leasing pipeline informs the vacancy forecast. A rent arrears pattern surfaces in the portfolio view without anyone exporting anything.

In one sentence

Fashti is an operational layer that handles the routine decisions and conversations of property management, inside your existing stack, under rules you control and with a record of everything it did.

Sits Above your systems Reads and writes through the interfaces your software already exposes.
Works in The channels work arrives on Portals, web forms, email, SMS and resident messaging, not a new app.
Governed by Rules you write Criteria, limits, tone and escalation thresholds are configuration, not guesswork.
Leaves behind A full audit trail Every action attributed to a trigger, a policy and a moment in time.

02 Anatomy

Six parts, working as one

The platform is deliberately unglamorous. Each part does one job well, and the value comes from them sharing a single picture of the portfolio.

01 Connectors Authenticated links into your CRM, property management software, mailboxes, messaging numbers, calendars, document storage and signature provider.
  • Scoped access, granted per system
  • Read only until you widen it
  • Changes written back, not duplicated
02 Portfolio model One structured view of properties, units, availability, rents, tenancies, residents, contractors and open work, assembled from the systems that hold each piece.
  • Units and tenancies as first class records
  • A single timeline per unit
  • Conflicting data surfaced, not silently merged
03 Policy engine Your operating rules in machine readable form: qualification criteria, what may be offered, notice periods, repair categories, spend limits, quiet hours and escalation thresholds.
  • Checked before any outbound action
  • Versioned, so you can see what changed
  • Different rules per property or owner
04 Conversation layer The part residents and prospects actually meet. It answers in your voice, in the channel they used, with the facts drawn from the portfolio model rather than improvised.
  • Email, SMS and web messaging
  • Consistent tone, set by you
  • Hands off cleanly when a person is needed
05 Work engine The part that does things: booking viewings, preparing agreements, raising work orders, scheduling contractors, issuing reminders and progressing renewals on schedule.
  • Every task tied to a unit and a tenancy
  • Retries and follow ups handled
  • Stops at any threshold you have set
06 Reporting layer Every action writes a record as it happens, so occupancy, pipeline, arrears, resolution times and workload are current by construction rather than reassembled at month end.
  • Portfolio, property and unit views
  • Owner reporting on a schedule
  • Exportable for your own analysis

04 Oversight and controls

You set the boundaries. The platform holds them.

Nothing about automation should be mysterious. These are the controls you get on day one, before Fashti is permitted to send a single message.

Permissions

Each connected system is granted its own scope. A connector that only needs to read availability is never given the ability to write to the ledger.

Approval thresholds

Decide what Fashti may complete on its own and what requires a person. Common thresholds are spend above a set amount, any rent concession, anything touching a notice or an eviction, and any first contact with a legal representative.

Tone and hours

Set the voice, the greeting, the signature and the hours during which residents may receive non urgent messages. Urgent safety matters override quiet hours by design.

Escalation rules

Name the conditions that must reach a human: a vulnerable resident, a repeated complaint, a habitability risk, a request Fashti has not seen before, or simply any message where confidence is low.

Audit trail

Every inbound message, outbound reply, decision, document and system write is logged with a timestamp, the triggering event and the policy that permitted it. Exportable, and retained on your retention schedule.

Reversibility

Any workflow can be narrowed or switched off without affecting the others, and without touching the systems of record underneath. Turning Fashti off leaves your data exactly where it was.

An illustrative queue. The rules that put items in it are yours.

05 Onboarding

From first call to first workflow

Four stages, run alongside your normal operations. Nothing freezes, and no work is migrated.

  1. 01

    Assessment

    One session, plus a written summary

    We walk through a normal week with the people who live it: where inquiries arrive, who answers them, what gets dropped, which systems hold what, and which parts of the job your team would never hand over. You receive a written view of what Fashti would take on first, what it would not touch, and where the connection points are weak.

  2. 02

    Connection

    Typically three to five working days

    Connectors are authorised against your systems with read access only. Fashti builds the portfolio model and begins shadowing live traffic, drafting what it would have said and done without sending anything. You compare its drafts against your own replies.

  3. 03

    Calibration

    One to two weeks

    Your rules are written into the policy engine and tested against real cases from the shadow period: qualification criteria, tone, what may be promised, when to stop. This is the stage that determines whether the platform feels like your team or like a robot, so it is deliberately unhurried.

  4. 04

    Handover, one workflow at a time

    From week two or three, then widening

    The first workflow goes live, usually inbound inquiry response. You review the exception queue daily at first, weekly once it is settled. Each further workflow is handed over only when the previous one is boring, which is the correct standard for operational automation.

What we need from you

  • An administrator who can authorise access to each connected system.
  • One operational owner who can decide what the rules should be.
  • Your current criteria for qualifying applicants, even if they live in someone's head today.
  • A review habit during the first fortnight, around fifteen minutes a day.

What you do not need

  • No data migration. Your records stay in the systems that hold them.
  • No new interface for the wider team to learn or live in.
  • No change of software. Keep the CRM and the property management system you have.
  • No pause in operations. Leasing carries on throughout.

06 Boundaries

What Fashti does not do

A platform that claims everything is hard to trust. These limits are deliberate, and we would rather you read them here than discover them later.

Not a property management system

Fashti does not hold your ledger, run your accounting or replace your system of record. If you are looking to change property management software, Fashti is not that purchase.

Not a decision maker on tenancy

It does not approve or decline an application on its own authority. It gathers, verifies against your criteria and presents a recommendation. The decision, and the responsibility for it, stays with your team.

Not a source of legal advice

Notices, disputes, evictions and anything touching a legal representative are escalated rather than answered. Fashti will tell a resident that a person will respond, and it will not improvise on the law.

Not a replacement for your team

It removes the repetitive middle of the job, not the judgement at either end. Viewings, difficult conversations, owner relationships and the decisions that need a person remain with people.

Not a silent operator

Fashti does not pretend to be a member of staff with a human name. Residents and prospects are told they are speaking with an assistant and can ask for a person at any point.

Start the conversation

See it against your own portfolio

A walkthrough is not a slide deck. We take a week of your real operational traffic, show you what Fashti would have handled, and where it would have stopped.

We read every message and reply within one business day