General inquiries
info@examold.com
Product information, demos, and partnerships
Contact
Tell us what you need and we will route it to the right team.
Use the form for course questions, technical help, pricing, billing, partnerships, or general product inquiries.
Every submission is saved directly to the ExaMold support backend for staff follow-up.
Learner support
support@examold.com
Content access, app issues, and troubleshooting
Support hours
Mon–Sat, 10 AM–7 PM IST
Messages can be submitted at any time
Office address
Powered by Floatger Technologies
2/412 J, Second Floor, SN Complex, Parayakadu PO, Cherthala, Alappuzha, Kerala, India, 688540
What happens next
A clear path from message to response.
We receive it
Your inquiry is recorded with its category and contact details.
We route it
Staff can assign and prioritize the message in the support admin.
We follow up
The appropriate team replies using the email or mobile details you provide.
App issueShare the device, OS version, app screen, and what happened before the issue appeared.
Course accessMention the course name, subject, plan, and the content or test you expected to see.
Pricing or billingInclude the plan name, payment date if available, and whether the issue is purchase, renewal, or invoice related.
Partnership inquiryTell us the organization, learner count, content format, and expected launch timeline.
Support routing
Clear fields help the backend route inquiries faster.
The public contact form sends only the display and support fields needed by the landing site, while staff can manage the full request from the backend.
Helps support separate app, course, billing, partnership, and general questions.
Makes the request easier to scan and assign from the support backend.
Email and optional mobile details help the team follow up clearly.
Device, course, plan, or screen details reduce unnecessary back-and-forth.
Inquiry types
Different questions need different context.
A short, accurate category helps the support backend route the message without asking the same clarifying question again.
Questions about mobile access, course content, revision, practice, or account support.
Questions about course publishing, Markdown descriptions, languages, and learning assets.
Questions about institutional access, learner groups, launch timing, or commercial discussions.
Questions about pricing periods, offers, invoices, renewals, or payment records.
Course and content
Course name, subject, language, page, or question details help the content team investigate.
App and device
Device model, operating system, app version, and screenshots make technical issues easier to reproduce.
Plans and payment
Plan name, billing period, date, and purchase platform help support check the correct record.
Keep one issue per message
Separate unrelated app, billing, and course questions so each can reach the right person.
Use exact labels when possible
Course name, page title, device model, plan name, and category make the message easier to resolve.
Avoid sensitive secrets
Do not send passwords, OTP codes, full card numbers, private keys, or unnecessary identity documents.
Helpful details
Include context that helps us solve the request faster.
For technical issues, mention your device, operating system, and the screen where the issue occurred. For course questions, include the course or subject name.
Never send passwords, OTP codes, complete card numbers, or other sensitive authentication information.