How RecUmi works
How it works
Each RecUmi product solves its own task and works on its own. When there are several, they exchange data through a shared foundation, RecUmi Core. Below is how it is built, and three scenarios with an honest status for every step.
Ecosystem diagram
- each product works on its own
- new directions — in the development plans
- RecUmi Calls is available first
- RecUmi CallsAvailable
- RecUmi VoiceIn development
- RecUmi ConversationsIn development
- RecUmi CRMNot publicly released
- RecUmi DocsIn development
- RecUmi MeasureNot publicly released
- RecUmi ServiceNot publicly released
The diagram shows the idea of the ecosystem. The status of each product is shown on its card; links between products appear as they are released.
TasksWhat tasks RecUmi solves
Information about a customer is scattered across calls, messengers, notebooks and employees' phones. Each RecUmi product takes one such area and makes it clear.
StandaloneEach product works on its own
Take only what you need
Need call recording? Install RecUmi Calls. Need measurements? RecUmi Measure will be there. No product requires installing the others.
We deliberately do not build one big program for everything: each product has its own screen, its own functions and its own way of working.
Add the others when you need them
When there are several products, they start exchanging data through RecUmi Core: the customer, the conversation, the measurement and the document end up in one history.
- As the company grows, it adds products rather than changing the system.
- Data already collected in one product does not have to be entered again in another.
RecUmi CoreRecUmi Core: the shared foundation
Independence
Each product solves its task completely and does not require installing the others. We do not pile everything into one overloaded program.
Shared foundation
What several products need at once will be kept in one place and not entered again: customers, employees and permissions, company details, document numbers.
Core is a direction of integration, not a separate app for the user. Links between products appear as they are released; for now RecUmi Calls works on its own.
The shared technology foundation: RecUmi Core
RecUmi Core is not a separate program for the user but the shared foundation of the ecosystem. Through it the products will know about the same customer, the same employees and a common document numbering.
- A customer created in one product will be recognised in another.
- Employee permissions will be set once for all products.
- Documents will get sequential numbers.
Core is a direction of integration. Links between products appear as they are released; for now RecUmi Calls works on its own. More about RecUmi Core.
What the shared foundation will provide
Core is not a separate app but a shared technology foundation. Its capabilities arrive step by step, as products are released.
| Area | What is planned | Stage |
|---|---|---|
| Organisations | Each organisation with its own legal entities, details, data and settings | Plan |
| Users | Inviting employees, sign-in, offices | Plan |
| Roles | Employee roles (for example manager, measurer, technician, head) shared by all products | Plan |
| Access control | Access is set once for all products; an employee sees what the work requires | Plan |
| Shared entities | One customer, site, catalogue of goods and services, files and documents for all products | Plan |
| Data | Each organisation's data, files, connected accounts and history are kept separately | Plan |
| Notifications | Unified notifications to employees about events in all products | Plan |
| Audit | Activity log: who changed what and when | Plan |
| Links between products | Exchange of events between Calls, Conversations, CRM, Docs, Measure, Service and Media; a single customer history | Plan |
| Future integrations | Connecting the organisation's external systems — for example 1C and advertising platforms — by a separate decision | Plan |
| Plans and AI features | A possible model of tiers and AI features per product — with no approved terms or prices | Idea, discussed earlier but not yet approved for development |
We do not name prices, plans or dates.
TogetherHow the products will work together
Below are the scenarios the ecosystem is designed for. These are planned capabilities: they will appear when the necessary products and the links between them are released.
From a call to a contract
A customer calls, and the company gets to a signed contract without retyping anything.
- CallsThe conversation is recorded, the customer's request is clear
- CRMA request and a customer record appear
- MeasureThe measurer takes dimensions and photos
- DocsFrom the measurement, a quote and then a contract
A customer's message is not lost
A customer writes to the company's WhatsApp, and the enquiry is assigned to an employee and lands in the customer's history.
- ConversationsThe new message is visible to the whole team
- ConversationsThe enquiry is assigned to an employee, the customer gets a reply
- CRMThe conversation is in the customer record
Repairs with a history
After installation the customer gets in touch again, and the performer sees what was already done and when.
- ServiceA repair request, a performer is assigned
- CRMCustomer history and past work
- DocsDocuments for the completed work
A document by command
An invoice for payment or a power of attorney, by voice or text, with a check before it is created in your 1C.
- CommandBy voice or text
- DocsA draft and the missing details
- ConfirmationYou check the preview
- 1CThe document in your organisation's 1C
- Finished documentPrintable PDF form
Completed work into an approved publication
Good work becomes material for social networks and the website, only with the customer's consent.
- CRMThe customer's order
- MeasureMeasurement and "before" photos
- ServiceWork done, "after" photos
- MediaA draft publication
- ApprovalThe responsible person confirms the platforms
From a meeting to tasks
A meeting recording becomes text, and what was agreed becomes next steps for the customer.
- VoiceA meeting recording with marks
- VoiceText and key decisions
- CRMThe next action on the customer
Scenario A: personal use
A conversation is not lost, and what matters is found by a word.
- CallA supported call is recorded on the phone; recording depends on the model and the Android versionWorks
- Listen and markLog, player, tags and notesWorks
- FindSearch by name, number, tag and words; transcription is a beta featureWorks
- Summary and taskA short summary and a task with your confirmationPlan
Transcription is a beta feature: accuracy depends on recording quality, language and device; it is not an artificial-intelligence analysis of the conversation.
Scenario B: sales
From the customer's first message to a contract, without re-entering data.
- WhatsApp enquiryThe customer's message in the company's shared listPlan
- Request in CRMCustomer card and an ownerPlan
- MeasurementDimensions and photos from the measurer's phonePlan
- QuoteA document from a template, built from the customer's and measurement dataPlan
- ContractFrom the same set of dataPlan
The whole scenario is planned. Some of its parts were tested in Time Rec's internal system, but the full path has not been completed in RecUmi products.
Scenario C: after the sale
Repair and installation with a history of work per customer.
- Customer and siteThe history of the customer and their addressesPlan
- Repair requestIntake and assigning a technicianPlan
- Visit and resultPhotos and the outcome of the work from the phonePlan
- HistoryThe work is kept in the customer's historyPlan
The whole scenario is planned.
Technical details
How speech is recognised
Recognition runs on the phone: with Android's built-in recognition if the language is installed, or with a Vosk model you have downloaded. Language models are downloaded only when you ask. If the only service available for a language is the system recogniser, which may process audio outside the phone, the app asks for your consent first — see the privacy policy, section “Speech transcription”.
Where data is stored
RecUmi Calls keeps recordings, transcripts and notes on your phone. What may leave the phone and when is described in the privacy policy, section “What may leave the phone”.
What does not work yet
Summaries, tasks, reminders and translation for RecUmi Voice, and links to customer cards and documents, are plans. We will announce each feature when it is ready and verified.
Postponed directions
The RecUmi ecosystem allows for new standalone products and directions to appear. Some ideas have been kept for future consideration. Their development and launch dates have not yet been approved.
Start with what you need today
RecUmi Calls is already available for Android. The other products are on their own pages, with the stage of each feature.