NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro

AI for education and training providers, from enquiry to certificate

A training provider or school knows its learners through a dozen tools: the enquiry in HubSpot or a Typeform, the course in Google Workspace, the session in Zoom or Meet, the payment in Stripe, the newsletter in Mailchimp. Memtro connects to them and answers the questions tutors and administrators ask every day, with each fact cited, so a learner's history is one question away and the records stay where they are.

7-day free trial · card on file, nothing charged until it ends · cancel any time

Students, courses, staff, documents and the ledger answered from one memory, with every figure cited to its record.

The systems these questions draw on, connected to one memory. Every connector reads by default; the tools that change something are granted by name, per team.

The problem

What it looks like today

  • 01A learner's enquiry, enrolment, attendance and payment are in four systems and the administrator is the join.
  • 02Which cohorts are under-enrolled a fortnight out is found too late to fill them.
  • 03Tutors answer the same questions about policy and process from memory.
  • 04Follow-ups promised to parents or employers live in an inbox.
  • 05An employer asks how their five learners are getting on, and the answer is assembled from a register, an inbox and a spreadsheet.
  • 06A tutor leaves and what they knew about how the course actually runs leaves with them.
How it works

What Memtro does about it

One memory in front of the systems you already pay for, reading by default and acting only where an administrator has granted the tool by name.

  • Connect Google Workspace, Google Calendar, Google Drive, Google Meet, Zoom, HubSpot, Typeform, Stripe, Mailchimp, Eventbrite and Gmail, reading by default and acting where you grant it.
  • Ask about a learner and the answer joins the enquiry, the enrolment, the sessions and the payments, each fact cited.
  • Policies and process documents in Drive are searchable from one place, and what was decided about them is remembered.
  • Google Calendar can create or move a session when asked; Gmail can draft the follow-up.
  • Schedule jobs: cohorts under capacity two weeks out, payments overdue by learner, enquiries without a reply in two days.
The stack

System by system

What Memtro reads in each part of the stack, and what it may change there once the tool has been granted.

The workspace

Google Workspace with Drive, Calendar and Gmail, or Microsoft 365 with Outlook, SharePoint and Teams: timetables, course material, policies and the mail around them, searched together.

Sessions

Zoom and Google Meet: who attended, how long a session ran and the transcript where the platform recorded one. Zoom can schedule, move or cancel a meeting once that tool is granted.

Enquiries and enrolment

HubSpot or Salesforce with Typeform: the enquiry, the form response, the follow-up and what became of each. Records change only through a granted action.

Fees

Stripe, GoCardless or Square: fees, instalments, failed collections and refunds, read by learner rather than by payout.

Open courses and events

Eventbrite: ticket sales, attendees and order totals for open courses, taster sessions and open days.

Keeping in touch

Mailchimp, Brevo or Klaviyo: campaigns, opens, clicks and who enquired again afterwards, joined to the enrolments that followed.

There are 144 connectors in all, each with its own tools, its own permissions and a page of its own. Browse every connector →

Who it is for

Who asks what

Course administrator

Answers a learner or employer question from the enquiry, the enrolment, the attendance and the payments at once, each fact cited.

Tutor

Asks what the policy is and where it is written, who has missed sessions, and what was agreed with a learner last term.

Admissions

Sees which cohorts are short, which enquiries match them and which never got a reply, in one list rather than three.

Head of centre

Watches enrolment, income and feedback together, and can show where every figure came from.

The work that comes round

From enquiry to certificate

  1. 01

    Enquiry

    A form response or an email arrives, and a daily job names anything older than two working days that nobody has answered.

  2. 02

    Enrolment

    A fortnight out, the cohorts below capacity arrive with the open enquiries that match them, which is early enough to fill a course rather than cancel it.

  3. 03

    Delivery

    Attendance comes from Zoom and Meet, materials and policies from Drive, and a tutor's question about either is answered with the document named.

  4. 04

    After

    Completion, feedback and what was promised to a learner or an employer are kept as memory, so next term's conversation starts from the record rather than from recollection.

In practice

Ask it like this

Plain English, from chat, your editor, a scheduled job or your own agent. In agent mode each question also checks the other systems that know about the same people, companies and references, and the answer ends with a line per system consulted.

Memtro · agent mode
Which courses starting in the next two weeks are below 70% capacity, and who enquired but did not enrol?
Reading 5 systems…
  • Google Workspace
  • Google Calendar
  • Google Drive
  • Google Meet
  • Zoom

Every figure in the answer cites the record it came from, and the run ends with a line per system consulted.

  • ›Summarise everything we hold on the learner Priya Shah: enrolments, attendance and payments
  • ›Which enquiries from the website form in the last week have had no reply?
  • ›What is our policy on deferrals, and where is it written down?
  • ›Who attended Tuesday's session, and who has now missed three?
  • ›What has the employer at BigCo asked about their five learners this term?
  • ›Which learners have an instalment that failed, and when were they last contacted?
  • ›What did last term's feedback say about the Level 3 course?
On a schedule

Work that runs itself

A job is a prompt the agent runs on a cron schedule as its owner, with their tools and connections. Say any of these in chat and the job exists; every run's report is kept in a chat you can question.

  • schedule:Every Monday 08:00: cohorts starting in 14 days below capacity, with open enquiries that match
  • schedule:Every day 09:00: website enquiries older than two working days without a reply
  • schedule:First of the month: learner payments overdue, grouped by course
  • schedule:Every Monday 07:30: learners who missed two or more sessions in the last fortnight, by course and tutor
  • schedule:Every Friday 15:00: enquiries from the last 30 days that never enrolled, with what each one asked about
How jobs work
Questions

Questions people ask

Is learner data protected?+

Each fact is classified personal or shared, connections are granted to named teams, and a request to be forgotten removes a person from every store, verified and receipted. You bring your own model keys, so prompts go to the provider you already have terms with.

Can it enrol someone or take a payment?+

Only where you grant it. The calendar can create a session, Gmail can draft a reply and HubSpot can update a record when asked; payments and enrolments are granted the same way as those actions arrive. Each action is granted by name per team, and a connector only reads until it is.

Does it work with a learning management system?+

Google Workspace and the tools around it are covered directly. An LMS with a reporting database is reachable over Postgres or MySQL, schema first.

Does it read attendance?+

It reads what the platforms record: Zoom and Google Meet participants and durations, and the transcript where one exists. A register kept on paper, or in a system with no database, stays where it is.

Can learners use it?+

That is not what it is for. It serves staff: members of your organisation, each with their own key, permissions and memory. Nothing is exposed to the public.

What about sensitive records?+

The connection is the control: a system is read only because you connected it, and a connection is granted to named teams rather than to everybody. Facts about an individual are classified personal, credentials are encrypted at rest, and a right-to-erasure request removes a person from every store with a receipt.

Next

The same work, by team

The same connectors and the same memory, described through the job somebody does rather than the business they do it in.

Memtro for education and training

Ask it about your own business

Connect the first two systems, ask the question you opened this page with, and see where the answer comes from. About five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time