marnis.ai

Small businesses

Phone, mail and website under control. Without an extra hire.

In a small business everyone does everything. A Node.Bot takes over what is always the same: answering calls, sorting mail, answering questions about your products. Your customer data stays in your shop.

A small shop: phone, website chat and mailbox all come together at a Node.Bot in the back room. It takes notes and sorts.

Examples

What your Node.Bot can take on.

Each example says what runs today and what comes next.

6 examples shown

Phone agent with follow-up questions

Planned

The agent picks up when you cannot, says that it is an AI, asks follow-up questions and writes you a short note.

Example: “Ms Berger would like to move the appointment on Thursday, preferably to the afternoon. Call back on the known number.”

Today
Talking to the bot in the web app and the iPhone app.
Next
An AI answering service on your own line, with a trial period before live operation. One line per Node at the start.

Customer requests to the right person

Idea

The bot reads incoming requests, recognises what they are about and gives the right colleague a ticket or an email with the key details.

Example: “Complaint about order 2318, photo attached, customer asks for a call back.” It goes straight to the workshop.

Today
Connecting mailboxes.
Next
Sorting is in progress. Forwarding to people is an idea and only comes after sorting.

An adviser on your website

Idea

A chat on your website that answers questions about your range using the current catalogue and is clearly labelled as an AI.

Example: “Do you also have the table in 1.80 metres?” “Yes, in oak and walnut, both in stock.”

Today
Nothing yet for visitors to your website.
Next
Product knowledge with verified facts is planned after version 1.0; embedding it on websites is an idea.

Check your website for weaknesses

Idea

Check your own website for known gaps, outdated parts and missing protection settings, with a report you can understand.

Example: “Your contact form reveals the server version. Here is how to switch that off.”

Today
Nothing yet.
Next
An idea. Only what belongs to you is checked, and only when you ask for it.

Plan appointments

Planned

Suggest free times and enter appointments, after your approval.

Example: “Next Tuesday or Wednesday morning is still free. Shall I accept?”

Today
Nothing yet.
Next
Calendar in the Secretary plugin: suggest times, enter them after your approval.

Research and preparation

Today

Compare prices, find suppliers, summarise documents.

Example: “Summarise the three quotes and tell me the differences.”

Today
Web search, summaries, and questions about code and spreadsheets in the chat.
Next
Learned routines for recurring tasks.

Honest maths

How many calls can a phone agent handle at the same time?

We are still measuring this, and we will not name a number before it has been measured.

What it depends on

  • Computing power of the NodeEvery reply in a call needs the language model for a moment. A Mac Studio with more memory can handle more of them at once than a Mac mini.
  • Queue per NodeCalls take priority over background work. The queue shares out the computing time so nobody waits for an answer.
  • More lines, more NodesIf you expect many calls at once, spread them across several Nodes in a Fleet.
  • One line per Node at the startThat is how the phone agent is planned. More calls per Node will follow only after measuring and a legal review.

Setup

What your setup could look like.

A Mac mini or Mac Studio

Depending on how many calls run at the same time.

Secretary plugin

Mail, calls, appointments.

One Bot per task

For example, Secretary and adviser kept separate.

Requirements in detail

Is this for you?

Join the waitlist. We will get in touch personally and talk about which tasks your Node should get first.

Join the waitlist