Or write here
One message, one engineer.
No routing, no tier one, no “have you tried clearing your cache”. The person who replies has the source open.
Contact
There is no ticket queue. Write to a person.
One address, four subject lines — and every one of them ends at somebody who can change the code. We are small, which is the only reason this is possible — and the reason we would rather you picked the right door than filed a ticket and waited.
Something is brokenhello@sokocode.com
A customer cannot book, a payment did not capture, the diary is wrong. Say what you
expected and what happened, and attach the site URL.Same day if critical
Before you buyhello@sokocode.com
Will it do the thing your business cannot work without? Ask before paying rather than
after. We will tell you when the answer is no.One day
You found a security problemhello@sokocode.com
Tell us privately first and give us time to ship a fix. We will credit you in the
changelog unless you would rather we did not.Same day, always
Migrating from another pluginhello@sokocode.com
We will sit on the dry run with you and read the report together. No charge, and no
sales call at the end of it.Booked within two days
Or call
Three numbers. One of them is a local call.
Pick whichever is a local call for you. All three reach the same people and the same inbox, around the clock — there is no line that only works while one country is awake.
Email is faster. Everything above reaches the same inbox and the same people, and a written description with a URL in it saves the call where we ask you for one.
Payments are authorising but the booking stays unconfirmed on one site. Started this morning.
Seen it — your gateway webhook is posting to the old URL. Fix is one setting, and I have written a reconcile for the eleven affected bookings. Deploying in ten minutes.
Replied in 38 minutes by the engineer who wrote the payment path.✓ resolved same day
What makes an answer fast
Not politeness — detail. The three things that turn a three-day thread into a one-reply fix:
The URL of the site it is happening on
What you expected and what happened instead, in that order
Whether it happens every time or only sometimes
Screenshots help. A screenshot of an error message helps more than a description of one. And if it is urgent, say so in the subject line — we read those first.
24×7 on anything criticalEvery time zone, every paid plan. Two hours to first reply on Practice, four on Team.
Support runs 24×7, in every time zone. Write at 3am in Chicago or midday in Berlin and somebody is on it — there is no queue waiting for an office in one country to open, and no “our team will get back to you during hours”.
Who answers
Three people. All of their addresses.
“The engineer who wrote the code answers your email” is only worth saying if we are willing to name them. The team page has the rest.
Vinod DoshiCEO & engineer
Chief executive, and still an engineer. Twenty years across software engineering, quality engineering, cloud, DevOps, automation and AI — at Microsoft, Amazon, Google, Adobe, Symantec, Zillow, Alcon, Vertex and Thryv. Founded and scaled a 40-person technology company serving clients across the US, UK, Germany, France, Italy, the Netherlands and India.
Vivek P.CPIO & engineer
Chief product and innovation officer, and still an engineer. A serial entrepreneur who has built businesses in farming, shipping and policy — three industries where the software was never the hardest part. Hands-on with hardware as well as interfaces, which keeps the roadmap honest about what a real counter, a real queue and a real pair of hands can actually do.
Rama VaradarajanCTO & engineer
Chief technology officer, and still an engineer. Two decades across frontend engineering, UI/UX, mobile, cloud platforms and AI-enabled products — React, TypeScript, Next.js, Node and Figma. He owns the architecture and what actually ships. He has led multidisciplinary teams from prototype through to delivery, and he is the one who says no to a screen that needs explaining.
Before you write
Half of it is already answered.
The documentation, the service levels, and an honest list of what is not built yet — which is the answer to more questions than we would like.