Skip to content
The workspace

One workspace for the unit list, the inquiries and the numbers. On the same inventory as your project website.

An inquiry arrives as a contact, a deal reserves its unit, and Insights counts both.

One example

One inquiry, five steps. From the project website to the sales numbers.

The inquiry arrives as a contact.

Anna Keller asks about unit 4.C on the project website. She appears in Contacts with her message and the unit she asked about. Her consent is stored with the contact.

Access

Who sees what. One workspace, three roles, and email that stays private until its owner shares it.

A mailbox decides who reads its email.

Pick a visibility and see what a colleague then finds on the contact's Email tab. The thread on top was synced after the change and follows it. The one below was synced before and keeps its visibility.

Your mailbox, in Settings

Visibility

Define what will be visible to other users in your workspace.

Visibility of the mailbox

The contact's Email tab, as a colleague sees it

The new thread: the colleague sees that it exists, without its subject or text, and a Request access button. The earlier thread is unchanged.

  • A connected mailbox starts private.

    Email synced from your Gmail or Outlook mailbox is visible only to you. Set the mailbox to Shared and everyone in the workspace can read the threads it syncs from then on. For a private thread, a colleague can request access and its owner approves or declines.

  • Notes and reminders can be private.

    A private note is seen only by the person who wrote it. A private reminder is seen only by the people it is assigned to.

  • Three roles: Admin, Member, Viewer.

    Admins also manage members, billing, settings, imports and exports. Members work with contacts, deals, units and projects. Viewers see contacts, deals, units and numbers and change nothing. An external broker is invited by email with one of these roles and uses one member seat.

  • Everyone sees every project.

    A person in the workspace sees all its projects and contacts, whatever their role. Access cannot be limited to one project.

Workflows

What runs by itself. A workflow starts on an event and works through the steps you gave it.

What can start a workflow.

An inquiry, a new or changed contact, a deal changing stage or a unit changing status. Or a schedule, a webhook from another system, or a person.

What a step can do.

Send an email from a connected mailbox, wait for a reply, wait a set time, branch on a condition, create or update a record, or call another system.

  • Only the contact's reply ends the wait.

    A “Wait for reply” step watches for an email from the contact. When one arrives, the run takes its “replied” exit and the follow-up is not sent. Out-of-office replies and mail from others on the thread do not count.

  • Each run is on record.

    A run lists its steps and how each one ended. A run that is still waiting can be stopped by hand.

  • Nothing runs until it is published.

    A new workflow is a draft, and a test run sends nothing. It starts when someone publishes it, and deactivating it stops its open runs.

The AI agent step is part of the Business plan.See pricing

The assistant

What the assistant may do. It answers from your workspace and changes nothing without your approval.

  • It asks before it changes anything.

    It may change unit statuses and prices, set a contact's status, assign contacts and add reminders. Each change comes as a card with the exact units or contacts, and nothing happens until you press Approve.

  • It stays within your role.

    For a Viewer it only reads and answers. The tools that change data are not available to that role.

  • It sends no email.

    The assistant and “Draft with AI” write drafts. A draft goes out only when a person presses Send, and then from that person's own mailbox.

  • It answers from your own data.

    Ask in plain language about availability, contacts, deals or how a project is selling. The answer comes from the projects, units, contacts and deals in your workspace.

Getting started

Start from what you have. A contact list, the architect's PDF and the website you already run.

Product screen. The contact import at its second step: each column of an uploaded CSV file is matched to a contact field, with a preview of its first value.

  • Contacts in and out as CSV.

    An admin uploads a CSV file, matches its columns to the contact fields and checks a preview. Rows whose email address is already in the workspace are skipped. The contact list exports to CSV at any time.

  • Contacts from your mailbox.

    A connected Gmail or Outlook mailbox can create contacts from the people you write to, and if you choose, from the people who write to you. It is off until you turn it on, and email from before the connection never creates new contacts.

  • Units from the floor-area PDF and a price list.

    The import reads the architect's floor-area PDF and drafts buildings, floors, units, rooms and areas for your team to review. Prices come from a price list.

  • Inquiries from the website you already run.

    Your current website can pass the inquiries from its form to Asono with an API key. A project can also have its own email address, and an email sent to it arrives as a contact. A new contact is filed under that project, and a sender who is already a contact is not added twice.

One workspace for the unit list, the inquiries and the numbers.

Import your contacts from a CSV file. New inquiries arrive from the project website.