Feature — Integrations & API

Integrations, API & on-premise deployment

Q: Can Qmeter run on our own servers?

Yes — Qmeter offers an on-premise option for Enterprise customers. The full platform is deployed on your own servers, inside your own network, so customer data never leaves your infrastructure and full control stays with your team. On-premise deployment is scoped as part of the Enterprise plan.

Q: Can we embed Qmeter into our own app or CRM?

Yes, two ways. The lightweight route is a Qmeter web survey opened from any screen, email, or receipt — one link, no app, no login. The deeper route is the API: keep your own UI and post responses directly, so feedback collection runs as a native part of your product. Both routes land in the same dashboard.

Q: How do we get call-centre or offline feedback into Qmeter?

Through External Feedback entry. Operators log phone calls, verbal comments, complaint-box notes, and social-media complaints directly into Qmeter in a few fields — so offline feedback joins the same dashboard as digital channels, and negative entries can still trigger automatic tickets.

Q: Will Qmeter build custom features for us?

If the feature makes the product better — yes. Tell us what your workflow is missing; if it fits, we build it, and it ships as part of Qmeter rather than a fragile one-off customisation. If it does not fit the product, we say so honestly. Custom scope is typically discussed alongside Enterprise plans.

Qmeter connects to any system through a REST API and webhooks, so feedback collection runs as a native part of your product, app, or CRM. Enterprises that need full control can run the entire platform on-premise — on their own servers, with their own data.

Feedback in from any touchpoint, events out to the tools you already use. And if you need a feature we don't have yet — tell us. If it makes the product better, we build it.

See pricing

1000+companies use Qmeter

2M+feedbacks collected

15+years in customer experience

REST API & webhooks

One customer feedback API — feedback in, events out

If your system can send an HTTP request, it can be a feedback channel.

The API is simply another channel in omnichannel feedback collection — responses from your systems land in the same dashboard as kiosk, SMS, email, and web feedback, and count toward the same NPS, CSAT, and SLI (Satisfaction Level Indicator).

Feedback in

Push feedback from any system

A mobile app, a POS, an IVR line, an internal tool — anything that can make an HTTP request can post feedback to Qmeter, tagged with the branch, service, and transaction it came from.

Events out

Webhooks for the moments that matter

When new feedback arrives or a ticket changes state, Qmeter notifies your systems — so CRM records, alerts, and follow-ups update in the tools your team already watches.

One picture

First-class channel, same analytics

API-collected responses appear in the same reports, branch comparisons, and AI analysis as every other channel. No side database, no export-import rituals.

Native feedback layer

Embed Qmeter into your product, app, or CRM

Your customers should never feel they have left your product to answer a survey.

Qmeter runs as the feedback layer of whatever you already operate — a mobile bank, a delivery app, an internal CRM. Use a lightweight web survey opened from any screen, or keep your own UI entirely and post responses through the API. Either way, every response is analysed, compared, and routed like every other channel.

Negative responses can flow straight into closed-loop ticketing, so a bad in-app rating becomes a tracked case — not a lost data point.

Open a survey from any screen, email, or receipt — one link, no app, no login
Keep your own UI and send responses through the customer feedback API
Tie every response to the branch, service, or transaction that produced it
Collect in 100+ languages with AI-assisted translation

Every channel counts

Call centre, front desk, complaint box — logged in seconds

Not every piece of feedback arrives digitally. External Feedback entry brings offline feedback into the same picture, so nothing stays invisible.

Call centre

An operator logs the complaint during or right after the call — rating, comment, branch.

Front desk

Verbal feedback recorded in a few fields before the customer reaches the door.

Complaint box

Paper feedback digitised into the same dashboard as every digital channel.

Social media

A public complaint becomes a tracked entry — and, where your rules match, a ticket.

Built with customers

Need a feature we don't have? Tell us.

Qmeter has grown for 15+ years by building what operators actually need.

Describe the need

Tell us what your workflow is missing — plain words, not a specification document.

We scope it honestly

If it makes the product better, we plan it with you. If it doesn't fit, we say so — no change-order theatre.

It ships as product

What we build becomes part of Qmeter — maintained and improved like everything else, not a fragile one-off customisation.

Large enterprise suites typically route custom work through consultants and paid change requests. With Qmeter you talk to the team that builds the product — see the Qmeter vs Qualtrics comparison for the wider picture.

Enterprise deployment

On-premise: your servers, your data, full control

Most teams run Qmeter as a cloud service and are live in a day. Banks, government bodies, and enterprises with strict data-residency rules can go further: the full platform deployed on-premise, on your own servers, inside your own network.

Teams searching for on-premise feedback software usually have one non-negotiable: customer data must not leave their infrastructure. That is exactly what this deployment is for — you host it, you control it.

On-premise pairs with Qmeter's security & GDPR controls — PII masking, audit logs, deletion workflows. It is scoped in the Enterprise plan and is a frequent requirement for banks and regulated industries.

The ROI

The return of not replacing anything

Integration ROI is mostly costs that never happen: no migration project, no parallel tools, no workaround glue code.

In the flow

Feedback that lives in a separate tool gets checked when someone remembers. Measuring experience inside the product, app or CRM you already run — where the work actually happens — is exactly what an API-first feedback layer is for.

not alongside it

Keep it all

Qmeter joins your stack through a REST API and webhooks; the CRM, POS and app you already operate stay exactly where they are. The largest hidden cost of a platform switch — replacing systems that work — typically never appears.

No rip-and-replace

Built in

A missing feature becomes a scoped product feature, not a fragile workaround. Large suites typically route custom work through consultants and change orders; with Qmeter you talk to the team that builds the product.

Custom development

Cloud plans are public — Web Feedback from €500/year, Device License from €50/device/month; Enterprise, including on-premise, is scoped per deployment. The figure missing from every price list is the cost of replacing systems that already work — that is the line an API-first integration deletes from the budget. See transparent pricing.

FAQ

Integration & deployment, answered

Short, honest answers. For anything else, talk to our team.

Does Qmeter have a customer feedback API?›

Yes. Qmeter’s REST API lets any system you run — an app, a POS, an IVR line, an internal tool — push feedback into the platform, and webhooks send events back out when feedback arrives or a ticket changes state. API-collected responses land in the same dashboard and reports as every other feedback channel.

Can Qmeter run on our own servers?›

Can we embed Qmeter into our own app or CRM?›

How do we get call-centre or offline feedback into Qmeter?›

Will Qmeter build custom features for us?›

Keep exploring

Get started

Plug Qmeter into what you already run

Start in the cloud today — live in a day, 14-day free trial, no credit card. Or talk to us about API scope, custom features, and on-premise deployment.