--- icon: phone --- # How to Reach Us The channels we monitor, what each is best for, and where to find us off the portal. ## Email Pick the address that fits the conversation. The two you'll use most are **`development@dmu.gr`** while a project is in flight, and **`customers@dmu.gr`** for the paperwork around it (invoices, proposals, account changes). If you're not sure, **`info@dmu.gr`** is a safe default — we'll route internally. - **[customers@dmu.gr](mailto:customers@dmu.gr)** — paperwork and account admin. Invoices we've sent you, payment questions, proposals, account changes, VAT and billing details, refunds — the office-side of being a customer. - **[development@dmu.gr](mailto:development@dmu.gr)** — project communications. The day-to-day of a project we're doing for you: progress updates, content you're sending us, content we're delivering, design feedback, technical questions about the build, change requests. The address to use when there's a project in motion. - **[business@dmu.gr](mailto:business@dmu.gr)** — business inquiries. New work you're not yet a customer for, partnership conversations, larger procurement discussions. - **[privacy@dmu.gr](mailto:privacy@dmu.gr)** — legal, data, and privacy. GDPR requests (access, export, erasure), DPA queries, anything covered in our [Privacy Policy](legal-and-policies). - **[hr@dmu.gr](mailto:hr@dmu.gr)** — careers and people-side topics. Apply for open roles or follow up on an application here. - **[info@dmu.gr](mailto:info@dmu.gr)** — general inbox. When none of the above quite fits, or you'd rather not pick — this lands with reception and gets routed. You can also reply directly to any thread you already have with us — that's the same as emailing the address above and keeps history together. ### Personal addresses Every member of our team has a personal `@dmu.gr` email, but we don't recommend them as the default contact path for customer questions. A specific person might be in a meeting, on holiday, or between things — meanwhile the shared inboxes are watched by whoever's around. **For most things, a shared address gets you a faster reply than emailing one individual.** That said, a direct message to a specific team member is the right choice in a few situations: - **Coordinating a meeting** with them. - **Private or sensitive project questions** you'd rather not put on a thread the whole team can see. - **Privacy-related matters** where you want to keep the audience narrow (alongside or instead of `privacy@dmu.gr`). - **Continuing a one-to-one conversation** you're already having with them — when the back-and-forth is faster direct than re-routing. For day-to-day work, default to the shared inbox that matches the topic. ## Phone **[(+30) 210 80 43 621](tel:+302108043621)** — our office line. Best for time-sensitive things during work hours, or when typing is slower than talking. ### Operating hours | Day | Hours | |-----------------|--------------------| | Monday – Friday | 09:00 – 18:00 | | Saturday | Closed | | Sunday | Closed | (Times are local to Athens, Greece.) ### If we don't pick up during hours It means we're busy with another customer or something hands-on at our desks. We'll call back as soon as we can — leave a voicemail with your name and the company you're calling about so we know who to reach. ### Outside hours The phone doesn't ring out-of-hours; it goes straight to voicemail. We don't have a 24-hour on-call line. We'll pick up your voicemail the next working day. If something genuinely can't wait until then, email ([development@dmu.gr](mailto:development@dmu.gr) for project / site issues, [customers@dmu.gr](mailto:customers@dmu.gr) for everything else) — we read email as the day starts and can sometimes respond outside hours when someone happens to be online, even though it's not guaranteed. ## Personal phones, social media, and messaging apps We respect our team's privacy and we ask the same of you. Please **don't** contact team members through their: - Private mobile numbers (calls, SMS). - WhatsApp, Viber, Signal, Telegram, or any other personal messaging app. - LinkedIn DMs, Instagram, Facebook, or other social media. These aren't work channels. Even if you happen to have someone's number or you're connected with them on LinkedIn from somewhere else, work conversations belong on the work channels above — the shared inboxes, the office phone line, or a personal `@dmu.gr` email in the specific situations listed in the *Personal addresses* subsection above. If a team member starts a work conversation on a personal channel themselves, you don't have to switch channels — but it's fair to ask them to move it to the work inbox for the next message. ## Visit **Kristali 7, Marousi.** Our office in Athens. Drop in if you happen to be in the area — but call ahead if you want to see a specific person, since the team's schedules vary. ## Contact page [**dmu.gr/support/contact**](https://dmu.gr/support/contact) gathers all of the above on a single public page, plus a short form if you'd rather type than open your email client. It lands in the same inbox as `customers@dmu.gr`. ## Support hub — for things that aren't a direct message Some asks fit a structured form better than free-form email. From the support hub at [**dmu.gr/support**](https://dmu.gr/support) you can: - **[Request information](https://dmu.gr/support/request-information)** — for when you're not sure what to ask, or where to begin. A short structured form to help us route you to the right person. - **[Request a proposal](https://dmu.gr/support/request-proposal)** — describe a project and we'll come back with a personalised, itemised proposal (scope, timeline, pricing). The same flow described in [Brief & proposal](../brief-and-proposal). - **[View status](https://status.dmu.gr)** — our public infrastructure status page. See [Service status](../services-and-monitoring/service-status). - **[View openings](https://dmu.gr/support)** — if you're here about working with us rather than working *for* us, the careers tile lists current open roles. ## Which channel for what A quick cheat sheet: | Situation | Best channel | |--------------------------------------------|-----------------------------| | Active project question | Reply to the thread | | Project progress, content, design feedback | `development@dmu.gr` | | Technical / integration / API question | `development@dmu.gr` | | Site down right now (in-hours) | Phone | | Site down right now (out-of-hours) | `development@dmu.gr` | | Invoice / payment / VAT / refund question | `customers@dmu.gr` | | Proposal / account / paperwork question | `customers@dmu.gr` | | GDPR / privacy / data-export request | `privacy@dmu.gr` | | New project we haven't scoped | `business@dmu.gr` or form | | Casual partnership inquiry | `business@dmu.gr` | | Career inquiry / job application | `hr@dmu.gr` | | General "I'm not sure where to send this" | `info@dmu.gr` | | Coordinating a meeting / private matter | The person's personal `@dmu.gr` | | Drop-in visit | Office (call ahead) | ## Outside business hours The phone goes to voicemail and we pick it up the next working day. Email is always open and we read it as the working day starts. We don't run an out-of-hours on-call line. If your site is down or something is critically broken at 11pm on a Saturday, email lands in our inbox and may get a reply from whoever's around, but it's not guaranteed until the next working day. Routine requests (a content tweak, a billing question) won't get a response until the next business day. See [Response times](response-times) for what to expect by channel.