Questions, answered properly

Implementation services. We design and build customer-relationship systems — websites and touchpoints, AI text and voice agents, lead capture and qualification, CRM automation, follow-up workflows, and the integrations between them — and then support them while they run. There is no product to subscribe to.

No. There is no Relnivo platform, dashboard, app, or free trial, and there is no account to create on this site. Everything we do is delivered as an engagement. If that changes, this page will say so.

With a free consultation. We ask how enquiries reach your business today, who handles them, and where you think customers are being lost. If we do not think we can help, we will say so in that conversation.

Small and medium businesses that receive enquiries through websites, forms, calls, messaging, and social channels. The clearest signal is simple: if a missed message is a lost sale, the work applies.

Our initial focus is businesses operating in Türkiye, and that is where our understanding of the market is strongest. If you are elsewhere, ask — but we will be honest about where our knowledge of local channels and expectations runs out.

Because scope varies by an order of magnitude between engagements that sound identical. We quote against a written scope produced at the end of solution design, so the number corresponds to something specific. If you have a firm budget ceiling, tell us early — it is a design constraint, and we would rather design within it than quote past it.

It depends on the number of channels, whether voice is included, the state of any existing CRM, how many integrations are needed, and how many languages content must be approved in. The largest variable is usually how quickly decisions come back from your side. You get a timeline with the written scope, not before it.

AI model usage, telephony for voice agents, messaging platform fees where they apply, hosting for anything we build, and subscriptions for tools the design depends on. These run on your own accounts and are billed to you directly at cost — we do not mark them up. We estimate them during design so the running cost is visible before you commit.

We re-scope and re-quote the change. We do not absorb it silently, and we do not let it stretch the timeline without saying why.

Yes. Every agent we build identifies itself as automated. A customer who believes they are talking to a person and discovers otherwise has been misled, and the damage from that outlasts any efficiency gain.

It hands over. The conditions are decided by you during design — a complaint, a price negotiation, anything clinical or contractual, or simply low confidence — and the person receiving it gets the full conversation, not a summary.

It can, which is why it is built against a knowledge base you approve rather than pointed at your website and left to infer. We test it against real cases before launch, restrict it from topics where a wrong answer is costly, and monitor it afterwards. Anyone who tells you an AI agent is never wrong is selling something.

The agent replies in the language the customer wrote in. For businesses in Türkiye that is usually Turkish and English, often with more. What matters is that you approve the content in every language you support — an agent answering in a language nobody on your side has reviewed is a risk, not a feature.

Yes, where the phone line can be conditionally routed — on busy, on no-answer, or outside hours. Voice adds telephony cost and a separate set of design decisions, so it is scoped explicitly rather than assumed.

You do. Integrations use credentials issued from your own accounts, customer data stays in systems you control, and nothing is created under a Relnivo account. If we stopped working together, the system keeps running and you keep everything in it.

Data flows between your systems and the services the design depends on. During solution design we document exactly what data goes where, so you can assess it against your own obligations. We are an implementation partner, not a data controller for your customers, and we are not in a position to give you legal advice about your obligations.

No. We hold no security, privacy, or quality certification and will not imply one. If a certification is a requirement for you, say so in the first conversation — it is better to establish that immediately.

No. Every scenario on this site is written by us to illustrate how a workflow would run, and each one is labelled as such. We publish no customer names, logos, testimonials, or results, because we have none we can evidence.

Monitoring and alerting on failures, adjusting conversation flows and rules as your services and prices change, extending the system when new needs appear, and regular reporting on what it handled. It is optional on a Simple engagement and part of the scope on Advanced and above.

Failures raise an alert rather than failing silently, which is the part that matters — a business that believes it is covered while an integration has been dead for a week is worse off than one with no automation. Response expectations are agreed as part of the support arrangement.

On a Simple engagement, often yes — you get handover documentation and training, and the system runs on your own accounts. On larger systems it is possible but rarely advisable, because multi-channel systems with several integrations drift and need someone watching them.

The system keeps running. Everything is built on your accounts with your credentials, so there is nothing to hand back and nothing that stops working because we are no longer involved.