As a member of the Wrike content marketing team, I receive no shortage of internal content requests. When other teams have ideas on how to promote Wrike or help customers use our software, guess who they turn to? You got it — me and my team.
.
Don't get me wrong, we love the suggestions and value the unique perspective each department has. However, work requests quickly piled up, coming in ad-hoc via Wrike tasks or cubicle drive-by. There was no way for us to dive into the goals that the requestor had in mind for a specific piece of content. Once Wrike Requests came along, it became a whole new ballgame.
.
Wrike Requests now allows us to standardize and prioritize content suggestions that come from other departments. With customized fields and templates, people are able to suggest their ideas and provide all the necessary info we need to execute it. Here are some ways our content marketing team uses Requests:
Requests for Blog Posts
We get a ton of TOFU (top of the funnel) blog post requests. Since our sales and customer success people are constantly in touch with customers, they always have fresh input on what content resonates with potential customers. Here are some sample fields we use in our blog post request forms:
- Name:
- Title:
- Department:
- Intended audience:
- Urgency of request:
- Description of blog post:
Requests for Sales Collateral
As we get down to the MOFU and BOFU content (middle and bottom of the funnel), it becomes really important for us to listen to the needs of our account executives and drill down into the details of the content. Requests allow us to get as specific as possible so we eliminate back-and-forth messages and get a clear idea of what we need to produce. Here are some additional fields we use in our sales collateral request form:
- Target Audience:
- Objectives:
- Event (if applicable):
- Planned Completion Date:
- Description/Additional information:
Requests for Case Studies
When customers are willing to do case studies, our team needs to know! When I first started, this was done via email or Wrike task, but this did not give us a way to learn more about the customer or gain context into their situation. Nowadays, teams can request a case study with an existing customer through Requests. Here are some additional fields we use in our case study request form:
- Priority:
- Customer company:
- Contact person:
- Customer since (date):
- Number of Users:
- Department(s) using Wrike:
- Customer Story:
Design Requests
Since most of our designers are overseas, sending them Requests is actually the most effective way to communicate what we need from them. Whether we need an infographic, or an eBook design, or even new social media images, Requests can be quickly inserted into the design team's pipeline. Here are some fields we use to request design materials:
- Planned Completion Date:
- Link to Content Task (if any):
- Asset Type:
- Target Audience:
- Target Channel:
- Call to Action:
- Notes/Additional Information:
Take a look at how to build your first Wrike Request form for a step-by-step guide on how to set up your first Request form.
.
.
For further reading, check out these related blog posts:
How would you use Wrike Requests to streamline your content needs?
Share your ideas with us in the comments.
