How to write and share tips and tricks
All CallTrackingMetrics community members are invited to post tips and tricks content on the community forum. These posts are detailed tips by CallTrackingMetrics power users to share information and resources. Examples of topics include things like specific workflows or call flows, business rule "recipes," customizations, troubleshooting solutions, unique ways to utilize features, and best or new practices.
These tips and tricks help grow and make the community a great resource for all users of the platform. And, if you post a high-quality tip, we may just send you some swag, feature it in the monthly newsletter or blog, and it may even turn into an article in the knowledge base! Sharing tips is a great way to build and demonstrate your technical expertise and get your knowledge published in a public forum.
To help you out, we've put together some best practices to consider when writing a tip:
Below are some general best practices for writing your tip:
- Break detailed posts into different sections.
- Add headings to your sections.
- Title your article with a clear description.
- Link to related documentation.
- Include step-by-step instructions.
- Include screenshots. (Should not exceed 600 pixels)
What to include in your post
One section you can include is the challenge or problem you faced. Then, readers can compare their situation to your own.
Content to consider for this:
- Describe how the problem originally occurred. What were you trying to accomplish before this problem or challenge happened?
- Explain how the problem or challenge affected your workflow.
After you discuss the challenge or problem, you can briefly describe the solution. This section is a good basis for your title.
Content to consider for this section:
- Provide a short description of the solution. This section should only define the solution. The following section will describe how to implement it.
- List any exceptions to the solutions. For example your solution could only work for users with triggers enabled or on a specific CallTrackingMetrics plan.
- Explain why the solution worked for you.
After you define your solution, you can then instruct readers on how to implement the solution. These steps are most effective when they are numbered and sequential.
Content to consider for this section:
- Include screenshots.
- Indicate any feature that needs to be enabled. Additionally, note if there are reasons steps might not work for users.
Thank you so much for sharing your knowledge with the community!
Comments
Post is closed for comments.