Contact
Contact and Feedback
Get in touch for support, product feedback, data corrections, SEO partnerships, and integration opportunities.
GetMoreDaysOff is built as a practical planning platform, and practical products improve fastest when users can report friction quickly. This page explains how to contact us, what information to include, and which channels are best for different requests. Whether you found a date issue, a route that should be improved, or a feature gap in planning workflows, your feedback helps prioritize meaningful releases.
We treat communication as part of product quality. A contact page should do more than expose one email address. It should make requests easier to triage, reduce response ambiguity, and set realistic expectations on what happens next. That is why we separate support, data-quality feedback, and partnership context while keeping the process simple enough for fast user reporting.
For multilingual audiences, clear contact architecture is also an SEO and trust signal. Search engines and users both expect transparent ownership, visible support paths, and coherent policy links. This page is therefore connected to our key planning and governance pages so users can move between assistance, legal context, and product workflows without losing continuity.
How to reach us effectively
- Primary support inbox: oubihis[@]gmail.com
- For bug reports, include URL, selected country and year, expected result, actual result, and screenshots if available.
- For data issues, include the affected holiday name, official source URL, country, region (if relevant), and date range.
- For partnerships, include audience profile, market focus, and specific collaboration objective so we can route quickly.
Support workflow and response quality
Fast support depends on structured context. When users include the exact page URL, route parameters, and reproduction steps, we can isolate issues more quickly and avoid back-and-forth loops. This is especially important in holiday-planning products where country, region, and year combinations change expected outcomes. We therefore recommend concise but complete reports that focus on environment, expected behavior, and evidence.
We prioritize requests based on impact and reliability risk. Data inaccuracies affecting active planning windows are treated urgently. Functional bugs that block core user actions, such as opening country hubs or loading leave-planner scenarios, are also escalated first. Lower-severity UI or copy issues are queued after critical fixes, but they remain valuable because they improve trust and completion quality over time.
Data correction and governance requests
Holiday and school-break datasets evolve, and regional policy updates can appear with little lead time. If you notice a discrepancy, sending the official source link is the fastest path to verification. We cross-check submitted evidence against our ingestion and normalization pipeline, then update where needed. This keeps planning outputs dependable while preserving traceability for future audits.
Governance-related messages are also welcome on this channel. If you need clarification about policy pages, data-source handling, or content ownership, include the relevant page path and your exact question. Clear governance communication reduces uncertainty for users, teams, and partners, and supports stronger multilingual SEO trust signals across the site.
Partnership and integration opportunities
We collaborate selectively with teams that share practical planning goals: travel publishers, HR communities, employee-benefit products, and data providers. Useful partnership proposals define audience overlap, expected value, and implementation scope. This allows us to evaluate relevance quickly and avoid vague discovery cycles that delay execution.
If your request involves content collaboration, include market focus and proposed distribution channels. If it involves product integration, include technical constraints and desired outcomes. We prefer scoped opportunities with clear user benefit, measurable impact, and realistic maintenance expectations.
Helpful planning routes
Link your support request to one of these pages so we can reproduce context faster.
Frequently asked questions
How fast can I expect a response?
We aim to review messages within two business days. Data-critical corrections and major product issues are prioritized first.
What is the best format for reporting a bug?
Use a short step-by-step reproduction list, include country and year context, and attach screenshots. This helps us verify quickly.
Can I request country expansion or new features?
Yes. Roadmap requests are welcome. Include your use case, expected workflow, and market context so we can assess impact.
Need actionable planning pages now?
Use countries and planner routes directly while we review your request. Most support questions are solved faster when linked to a specific page.