Skip to content
Custom service

Connect your tools and cut down manual work.

We review the process that takes up your time and define how to solve it. We can combine your tools, specialised services and Darcemi development.

It's an independent service: you don't need to contract another Darcemi solution.

Illustrative example An automation in three steps. The connections and the result are defined after reviewing your case. Three steps. Data or events leave the tool you already use, through its API or an export. Fields, permissions and rules are checked before the connection is switched on. And they arrive as a record or an alert in the agreed destination, with its review and follow-up.

What an automation gets you

  • Fewer repeated tasks

    What you copy by hand between tools today, solved and checked.

  • Scope in writing

    What gets automated, what doesn't, what it costs and who answers if something fails, before we build.

  • Tested before switching it on

    We validate it with you using your data before it goes live.

Processes to assess

Which tasks we can look at.

They're examples to guide your request, not ready-made connectors for any tool. The scope is confirmed in the review.

Copying data between programs

Today
You copy clients, orders or records by hand from one tool to another.
What we aim for
Each piece of data entered only once.
What we check first
Whether both tools allow reading and writing that data in an authorized way, and what it costs.

Notifying when something happens

Today
Someone checks by hand whether something happened to tell the team or the client.
What we aim for
The notice goes out by itself when it happens.
What we check first
Where the event comes from, which channel sends the notice and what that channel costs.
A capability we've built

Available import: data from DocFav.

We've built a dedicated import from DocFav. This example shows which data it accepts, how it's reviewed and what's left out.

  1. Where it starts

    A business working with DocFav keeps its clients, team, services, booked appointments and past invoices there. Entering it all again by hand means a lot of work and room for mistakes.

  2. What's been built

    An import in two parts. The calendar comes through the DocFav API with the business's key. Past invoices come from the issued-invoices Excel file and the PDFs DocFav exports.

  3. What's available

    Clients, team, services, appointments from the import date and calendar blocks, and previous invoices as closed invoices, with each series' numbering so you can keep issuing.

  4. What's still human work

    Reviewing how team and services are matched, setting hours for professionals who arrive without them and loading active session packs. What DocFav doesn't export, such as clinical records or past appointments, isn't moved.

  5. How it's checked

    Before applying anything, a review shows what's matched, the rejected rows with their reason and the invoices with a warning. What's imported is marked with its origin and the import can be undone.

It's a one-off migration, not a sync: the data is brought in once and the DocFav key is deleted at the end.

Scope

What the service includes

Every project is different. The method is the same.

Review

  • What's done today, with which tools and where time is lost.
  • What each tool allows: API, exports and permissions.
  • Whether it's worth automating, before we quote.

Proposal

  • Scope, cost and timing in writing.
  • What's left out and who answers if something fails.
  • Which providers are involved and what they charge, if anything.

Build and maintenance

  • Configuration, connections or development, as the case requires.
  • Tests with real cases before going live.
  • Maintenance on the terms we agree.

Darcemi sets it up. We combine what you already use, specialised services and our own development. Not everything is built from scratch and not every project uses AI: we choose what solves the process.

Getting started

How we run a project

How it starts

  1. Review

    We understand the process and check what each tool allows.

  2. Scope and quote

    What gets automated, what doesn't, what it costs and who answers if something fails.

  3. Build and validation

    We develop it and test it with you before it's used for real.

  4. Launch and maintenance

    We switch it on and maintain it as agreed.

See how we work

Connections

  • What Darcemi already connectsIncluded

    WhatsApp Business, Google Calendar, VeriFactu through Verifacti and the DocFav import. If your process goes through these, we start from something that already works.

  • Tools with an APIAssessed during the review

    Software that allows reading or writing data in an authorized way. It's the most common case.

  • Export filesAssessed during the review

    When there's no API, sometimes an Excel or CSV file imported regularly is enough.

Conditions

Good to know before you start

Before committing to a connection we check what the tool allows, which permissions are needed, what it costs and who answers if it fails.

What you need

  • Access to the tools to connect, with permission to do so.
  • Someone in your business who knows the process.
  • Test data, or a safe way to validate with real data.

What's not included

  • Connections the source tool doesn't allow, because of no API or no permissions.
  • An ERP, a phone system or an inventory system built from scratch.
  • Open-ended maintenance without an agreement. It's agreed for each project.

Which costs apply

Review
We review the process and tell you whether it's worth automating before quoting the development.
Development
Depending on what needs connecting, configuring or developing, and validating.
Maintenance
If you want it, a recurring service with what it covers in writing.
Third-party costs
Whatever the connected tools charge for using their API, if anything.
How the cost is worked out
Questions

Frequently asked questions

What kind of tasks can be automated?

Ones that repeat and follow clear rules: moving data from one tool to another, sending a notice when something happens or preparing a document from data that already exists.

Can I come from other software?

We can review your case even if your software isn't among the current connections. First we check the files it can export, the permissions and the integration options. Then we set out what can be moved or connected and what work it takes.

What if my software has no API?

Sometimes we can work with its exports. If there's no authorized way to access the data, we tell you in the review and don't quote it.

Do you build everything yourselves?

Not always. We combine your tools, specialised services and our own development. Who does what is set out in the proposal.

Who maintains the automation?

We agree it for each project: what maintenance covers, what it costs and what happens if the other tool changes.

Do I have to contract another Darcemi solution?

No. It's an independent service.