Buy or evaluate
I am considering Omnetic
Pricing, scope, migration, market and brand mix. The sales team for the country receives the request.
Or send a written enquiry
Omnetic · Contact
A customer with a broken invoice run and a prospect comparing systems need opposite context. Choose the reason first; the right form or channel comes afterwards.
Buy or evaluate
Pricing, scope, migration, market and brand mix. The sales team for the country receives the request.
Or send a written enquiry
Existing customer
A problem belongs in the in-product help desk, where instance, version and ticket history are attached. A marketing form would lose that context.
Emergency line, business hours
Deliberately not a form on this page. A form here loses the instance ID and adds a day.
Partnership
Technology integrations, OEM programmes, accounting and classified connectors, implementation and resale.
Read the API docs first
Media & company
Interviews, benchmark methodology, brand assets and research belong with the press contact.
Brand & logo pack
All nine current addresses, a verified local email and a direct maps link.
Dělnická 1628/9170 00 Praha 7
Answers in Czech or English.
obchod@omnetic.comPribinova 8811 09 Bratislava
Answers in Slovak, Czech or English.
kancelaria@omnetic.comKarl Waldbrunner Platz 11210 Vienna
Answers in German or English.
sekretariat@omnetic.comKieselstraße 1341472 Neuss
Answers in German or English.
handler@omnetic.comAleje Ujazdowskie 4100-538 Warsaw
Answers in Polish or English.
polska@omnetic.comGustav Mahlerplein 21082 MA Amsterdam
Answers in Dutch or English.
office@omnetic.comCorso Europa 1520122 Milan
Answers in Italian or English.
ufficio@omnetic.comCarrer de la Marina 16-1808005 Barcelona
Answers in Spanish, Catalan or English.
oficina@omnetic.comBulevardul Dimitrie Pompeiu 5-7020335 Bucharest
Answers in Romanian or English.
birou@omnetic.comThe current site lists officers by name on the contact page. Direct addresses for named individuals stay off the public page. They attract recruiters and spam, not customers, and every one of them ends up answered by an assistant anyway.
Route by function instead. If a specific officer is genuinely needed, the function inbox reaches them in one hop and the request arrives with context.
Contract, pricing or account issues above the account manager; reaches the CSO's office.
DPA requests, subprocessor list, incident reporting and vulnerability disclosure.
Feature requests and roadmap input from customers; reaches product, not support.
Contracting entity for the market, VAT ID and purchase-order handling.