Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

Integrations

Showing 18 of 1804

Quip Integration

We use Quip for document collaboration and would love to see support in the Content tab. That would allow us to seamlessly create, edit, review, and approve documents without having to move files.
over 1 year ago in Content Marketing / Integrations / Tasks, Campaigns, and Events 0 Future consideration

Veeva Task Names from Welcome

When creating an asset in Welcome and syncing it to Veeva, use the task name from Welcome, not the filename of the asset.
over 1 year ago in Content Marketing / Integrations 0 Future consideration

Miro Integration

Miro we can turn a card into a task (Issue) in Jira and that's really great. I would love it if we could do the same with Welcome.
about 2 years ago in Content Marketing / Integrations 0 Future consideration

Preview Image for Twitter Posts

Does Welcome plan to incorporate the preview image function for Twitter posts? Currently, the right hand side preview pane in publishing tab for the Twitter widget currently does not expand to show the thumbnail preview of the URL that is pasted.
about 2 years ago in Content Marketing / Integrations 0 Future consideration

@-mentioning in Facebook and LinkedIn Posts

We'd like the ability to @-mention users on Facebook and LinkedIn, like we can with Twitter. Today, we have to go into those tools directly to edit posts if we want to @-mention someone. Having it in the system would save us a lot of time.
over 2 years ago in Content Marketing / Integrations 0 Future consideration

API: Provide Readable Object IDs

Currently, the platform provides a persistent ID for label groups and labels values but those are not user-friendly, which makes troubleshooting and development complicated and prone to errors. Having the ability to define at time of creation or m...
over 2 years ago in Content Marketing / Integrations 0 Future consideration

Surface Task and Article GUID in Feeds

We are currently publishing via a feed and will be collecting “Applauses” (feedback from readers) on the site. We are looking to populate that number in the CMP using the API. But we can't, because the feed doesn’t surface the Article GUID nor the...
almost 3 years ago in Content Marketing / Integrations 0 Future consideration

Expose the Account ID that has been used to authenticate Salesforce

We really need the Account ID visible on the front-end so that if another admin team member needed to make any adjustments or we had connection issues, they'd be able to troubleshoot effectively. A user recently tried to integrate but CMP auto aut...
over 2 years ago in Content Marketing / Integrations 0 Future consideration