Customization

It adapts to the way you work. No coding.

Your document types, your fields, your screens, your checklists and your vocabulary. It all lives in configuration, not in custom code. That is why attendo keeps getting updates no matter how much you adapt it.

Request a demo See what you can configure

No custom code
Kept through every update
Each profile sees only its own

attendo settings screen with the organization, work, sales and documents blocks, catalogs, custom fields and templates. — Settings, by block: organization, work, sales and documents, catalogs, custom fields and templates.

The problem

Rigid or custom-built: two ways to lose

Rigid software forces you to change your process to fit it. Custom-built software fits on day one, breaks with every update and depends on whoever built it. attendo takes a third path: it is configured, not programmed.

Configuration

What you can configure

Document types

You decide what each thing is

A ticket, a work order, a case file or a construction job. Each type has its own menu, icon, color, fields and workflow.

You choose which blocks appear on the record and in what order, and which views it uses: table, board or calendar. The screen is composed, not coded.

Settings screen with organization, work types, catalogs, custom fields and templates — Settings: document types, fields, catalogs and templates, without touching code.

Solutions

Nine built in, plus your own areas

Ticketing, Customer Service, CRM, After-Sales, Field Service, CMMS, Projects, Compliance and Flows each come with their home screen with KPIs, their reports and a dashboard you can edit. You can also create your own areas with their name, icon and home screen.

User profiles

Each person sees their own

On a single screen you decide which menu, home screens, dashboards and reports each person sees, and which options are hidden from them. For desktop, tablet and mobile.

Fields and screens

The data your operation needs

Custom fields with permissions by role, required when needed, and visible, read-only or hidden in each portal. Lists filter by any of them.

Your organization

Companies, groups, lines and workspaces

Several companies, work groups, business lines, workspaces and industries in the same instance. Each person works in the ones that concern them, with each company’s or line’s branding.

Labels and diagrams

What gets printed and drawn, too

You design your labels like the rest of the templates: format, fields and QR code or barcode. And process and flow diagrams adapt to your operation.

Whiteboards

To think together, on the record

A page the team writes at the same time, showing who wrote each part and what changed, with versions. Or a canvas to draw on together over a photo or a floor plan. Linked to documents, customers, projects, people and groups.

A tag is not a name. It is a record.

A piece of equipment, a customer or a location has its own fields, what is linked to it, the documents opened on it and a template that can be copied to another customer. Pick a solution and look at the four layers.

Example What’s behind a tag

01 · Information

It has its own record

The equipment tag keeps its fields: the built-in ones and any you add.

Asset AST-0418

Booster pump BP-02

Family: Pumping
Location: Building 2 · plant room
Serial no.: SN-4471-K
Warranty: Until Mar 2027

02 · Relationships

It’s linked

The customer who owns it and the maintenance plan: they open from the tag itself, with no searching.

Asset AST-0418 Booster pump BP-02

Customer CU-0231 Owner · active contract
Plan PM-QTR-07 Quarterly preventive · ±5 days

03 · Context

It builds up what happens

Every work order opened on the equipment stays in its history: who, when and what was used.

Corrective WO · WO-2026-0142

Vibration and seal leak

In progress

2 photos
1 spare part
Checklist

Linked to

AST-0418

CU-0231
PM-QTR-07

04 · Template

It copies in full

A tag template carries fields, links and tasks over to another customer in one go.

Tag template One step

Booster pump

Technical fields
Linked plan
Tasks

New tag for CU-0307

Checklists and templates

Your inspections, your documents

Free-form checklists with photos, QR codes, geolocation, range alerts, conditional logic and versions. Task templates by type. And a print designer where you drag fields to build your quote, your service report or your delivery note, with QR codes and barcodes.

List of print templates with their data source, page size and status: business document, asset record, project report, ticket report and delivery note. — Print templates by data source: business document, asset record, project report, ticket report and delivery note.

Vocabulary and languages

attendo speaks like your team

If your team says “case file”, attendo says “case file”. You rewrite any text or change a term across a whole language, with a preview. After each update, a glossary flags new texts that use the standard word. The portals also have their own words. Spanish, English and Catalan come standard, and you can add languages.

Your brand

On every screen your customer sees

Logo, colors, font and legal footer by company, business line or issuing company. Emails, web quotes, payment pages and portals go out with the brand of whoever issues them.

Modules

What you do not use does not appear

You turn on only what you need, and the rest takes up no space in the menu. Settings have a search box and each screen explains what it is for.

marIA

AI in configuration

Complete with AI

Translates missing text into another language and never overwrites what a person wrote.

marIA Flows

Draws the flow you describe in plain language.

See automation

Every marIA operation is logged with its cost, and spending stops at the cap you set. See how AI is controlled

Onboarding

Configured for you, and repeatable

Implementation follows a step-by-step onboarding wizard, with the questions that define your operation. The result is a template that is simulated before it is applied and never overwrites what already exists.

Industry demos that install in one click and are deleted without touching your data
Import and export from Settings: users, customers, suppliers, contracts, products, assets, plans, rates and documents with their history
The same file works both ways, and it is checked in full before anything is saved: each row with an error says why

Limits

Where it fits (and where it does not)

Configuration by API
Configuration is not done by API: it is done in the settings, on desktop.
Critical screens
Critical administration screens are protected with step-up verification. Your implementation partner handles them.
History from another program
Document history from another program is not imported automatically. It is scoped as a project.

The rest of the platform

And when you need it, the rest is already here

Frequently asked questions

If we customize it a lot, will we lose the ability to update?

No. The configuration lives in data, not in modified code. A heavily customized instance updates just like a standard one.

Do we need to write code?

Not for document types, fields, screens, checklists, printing or flows.

Do we depend on the partner for every change?

No. Your administrator handles day-to-day configuration. Only the critical screens, such as module activation or the flow editor, need your partner.

It seems too big for us.

It is modular. You start with one area, each profile sees only its part and what you do not use does not appear.

Can we call things by the names we use?

Yes. You change any term across the whole platform, with a preview.

Can we load our data without depending on you?

Yes. From Settings you download the template for each item, fill it in and validate it: validation saves nothing and returns the errors row by row. Whatever you export can be imported back as is.

Is each solution a separate program?

No. Each solution, such as CMMS or Customer Service, is the same engine with that work’s home screen, reports and dashboard. You turn on the ones you subscribe to, and one person can have several and choose their own.

Cookie settings