Contact Us
Need to reach JamForce? This page explains what to send, when to expect a reply, and how your message is handled.
What You Can Contact Us About
Section titled “What You Can Contact Us About”Use this form for:
- Questions about Salesforce articles and guides on this site
- Requests for corrections or updates to existing content
- Partnership or collaboration enquiries
- General feedback on site usability and learning paths
The corrections policy explains how reported errors are checked and how material corrections are recorded.
Response Expectations
Section titled “Response Expectations”- We usually reply within 2-5 business days.
- Complex technical questions may take longer if research is needed.
- If your message is urgent, include
URGENTin the subject line of your message.
Contact Form
Section titled “Contact Form”Before You Send
Section titled “Before You Send”For a faster and more useful reply, include:
- The page URL you are referring to (if relevant)
- What you expected vs what you saw
- Your Salesforce context (Admin, Developer, Architect, or learner)
- Any error text or screenshots (describe them in your message)
Privacy and Data Use
Section titled “Privacy and Data Use”Messages submitted through this form are processed by Formspree so we can respond to you. We only use contact details to handle your enquiry and follow-up where needed.
Read our full Privacy Policy and Terms of Service.
Contact FAQ
Section titled “Contact FAQ”Do you provide one-to-one Salesforce consulting?
Section titled “Do you provide one-to-one Salesforce consulting?”JamForce is primarily a learning resource. If you have a consulting enquiry, share your scope and we will let you know if we can help or refer you onward.
Can I request a new article topic?
Section titled “Can I request a new article topic?”Yes. Topic requests are welcome and help shape future guides and blog posts.
I found an error in a guide. What should I send?
Section titled “I found an error in a guide. What should I send?”Send the page link, the section heading, and what appears incorrect. If possible, include the expected behaviour and an official source, Salesforce release, or API version that supports the correction. The corrections policy explains what happens next.