Contact Wemaxa for web design, development, AI and support.
Use sales@wemaxa.com for new work, enterprise@wemaxa.com for larger systems and integration-heavy projects, support@wemaxa.com for active technical support, and info@wemaxa.com for general company questions.
Message routing
A project brief moves from visitor input to review, classification and sales reply.
New project conversations
For a new website, redesign, application, ecommerce build, AI integration or branding project, sales@wemaxa.com is the default route. Include the current URL if there is one, the main outcome, must-have features, target timing and any examples that help communicate the desired level of design. If the project has an approximate budget range, include it so the first response can be commercially realistic.
The Start a Project page can assemble the same information into a prefilled email if you prefer a structured brief. A detailed specification is not required for initial contact. It is enough to explain the business problem and any hard constraints.
Enterprise and integration-heavy work
Use enterprise@wemaxa.com when the project includes several systems, multiple user roles, data migration, enterprise identity, infrastructure requirements or a discovery phase. A short architecture summary is useful even if some details are still unknown. List the major systems and which team owns them.
Do not send production passwords or confidential datasets in the first email. Describe the categories of data and the access requirements instead. Credentials and sensitive files can be exchanged through a secure project channel if the engagement proceeds.
What the work actually involves.
Existing support requests
Active maintenance and technical issues can use support@wemaxa.com, ideally in the existing project thread where previous context is available. A useful support request identifies the affected URL or feature, the action attempted, the expected behavior, the actual result and any visible error message. Screenshots can help when the issue is visual.
Wemaxa's public customer-care policy does not promise 24/7 live support. If a project requires defined response times or emergency coverage, those expectations need to be part of a maintenance agreement. Sending the same issue through several channels does not create a faster technical diagnosis.
General information and routing
General company questions that are not sales or support requests can use info@wemaxa.com. If you are unsure which address applies to a new commercial conversation, sales@wemaxa.com is the safest starting point. Wemaxa can route the message internally if the request belongs with enterprise work.
The live site has shown different phone numbers in older pages, so this rebuild deliberately does not present an uncertain phone contact as a primary channel. Email addresses are kept because they are consistently published across the current service and maintenance material.
What to include, and what to keep out
For sales, include enough business context to understand the project. For support, include reproducible technical context. For enterprise, include systems and stakeholders. In every case, avoid placing passwords, API keys, payment credentials or private customer data into an unsolicited email.
If access is eventually required, the project can use a secure credential-sharing process. This protects both the client and the agency and avoids leaving long-lived secrets buried in ordinary email threads.
Use sales for new commercial work
sales@wemaxa.com is the main address for new website design, redesign, full-stack development, ecommerce, applications, AI integration, branding and related commercial projects. A useful first message includes the current URL, primary goal, approximate scope, target timing and any hard platform requirements.
If the project includes AI, describe the workflow and data rather than only saying that the site needs AI. That gives the team enough information to determine whether the work is a simple API integration, retrieval system, internal assistant, tool-using workflow or a larger application feature.
Use enterprise for integration-heavy systems
enterprise@wemaxa.com is appropriate for systems with several user roles, legacy migration, identity integration, internal APIs, deployment constraints, stakeholder coordination or a discovery phase. Include an architecture summary if one exists, but an incomplete description is acceptable when discovery is part of the need.
Do not send production credentials or confidential datasets in the first email. The team can arrange an appropriate access channel after the scope and responsible contacts are established.
Use support for active operational work
support@wemaxa.com is intended for active maintenance and technical-support conversations. Existing clients should continue the project thread when possible because it preserves previous context, deployed versions and third-party account information.
Support for an external vendor outage is necessarily different from support for Wemaxa's own code. The team can diagnose integration impact and help with recovery steps, but the third-party provider remains responsible for its service.
General company questions
info@wemaxa.com can be used for general information that is not a project inquiry or active support request. If the right destination is unclear and the message concerns new commercial work, sales@wemaxa.com is the simplest starting point.
The site intentionally separates these channels so a production support issue does not compete with a new-business conversation in the same queue.
What to include for a website redesign
For a redesign inquiry, include the current URL, the main reasons for changing it, the parts that must be preserved and any examples that communicate the desired level of design. If the existing site has search traffic, multilingual content, forms or important integrations, mention them. This helps distinguish a visual refresh from a migration project that also needs URL redirects, content restructuring or platform work.
What to include for AI integration
For an AI inquiry, describe the task, data source and allowed action. Examples are more useful than broad requests to 'add AI'. Explain whether users are public or authenticated, whether the model needs internal documents, whether outputs enter another system and whether a human must approve an action. If sensitive data is involved, describe the category and handling requirement without emailing the confidential records themselves.
What to include for a custom application
For an application, list the main user roles and the important workflow. State whether users need accounts, whether there is an existing database or API, which third-party systems must connect and whether data needs to be migrated. A rough diagram or bullet list is sufficient for the first conversation. Detailed architecture can be developed during discovery.
What to include for support
For an active support issue, include the affected URL or environment, what was expected, what happened instead, when it began and whether anything changed immediately before the problem. Screenshots and reproducible steps can help, but do not include passwords or private keys. If the issue concerns an external provider, include the relevant error message or provider status information when available.
What we clarify before committing to the build.
Questions that usually affect scope.
Which address should I use for a new website?
Use sales@wemaxa.com or the Start a Project page.
Which address is for enterprise work?
Use enterprise@wemaxa.com when the project involves larger systems, several integrations, migration or enterprise discovery.
How do I report a support issue?
Use support@wemaxa.com and include the URL or feature, reproduction steps, expected result, actual result and any error message.
Is there guaranteed 24/7 support?
No universal guarantee is published in this rebuild. Specific response expectations need to be part of a maintenance agreement.
Can I send credentials by email?
Do not send production passwords, API keys or confidential datasets in the first contact message.
Conversation path
The secondary scene shows a short path from question to context to response.
Discuss contact with Wemaxa.
Send the project brief or open a direct sales conversation.