We’re constantly updating our product to make it better and easier for our clients to implement and customize, and for our clients’ customers to use. While you can keep up with these changes day-to-day in our changelog, we’ll use this monthly round-up to recap key updates and tease upcoming features.
Have something you’d like to see on our roadmap? Get in touch with us at sales@cord.com.
1. We optimized our screenshot capabilities
You asked for more control over screenshots, and we delivered. Here’s what’s new:
- Developers can now choose when to take a screenshot. Previously, the behavior was set to take screenshots when a user created an annotation or when they shared a thread via email. But now, by specifying “new-message” or “new-thread”, developers can trigger a screenshot whenever a new message is sent, or a new thread is created.
- Thanks to Cord’s new ScreenshotConfig API, developers can also choose what to take a screenshot of by setting a target element. And if you want to remove irrelevant stuff captured in a screenshot after it’s been taken, you can by using the “cropRectangle” property, hiding parts of the “targetElement”, or adding some padding around it. Simple!
- Finally, developers can override Cord’s screenshot process altogether and instead provide their own. Learn more here.
2. We enabled white-label email domains
Let’s say an Account Executive at Chili Piper is using trumpet to communicate with a prospect. Since trumpet uses Cord’s APIs to power its collaboration features, that AE can be notified whenever someone replies, reacts, or @ mentions them in a comment or thread. Until now, an email alerting him or her of the notification would reference Cord in various places in the body and header.
But now that we’ve enabled white-label email domains for premium customers (check out our pricing model here), you can send notification emails from your domain instead of ours. This encourages more engagement (that AE from Chili Piper is a lot more likely to recognize and trust an email from trumpet than Cord), creates a more seamless user experience, and gives our customers one more opportunity to put their brand front and center.
Are you an existing customer who wants to roll this out? We’re here to help, just ask!
p.s. You can see how trumpet is using Cord’s features to supercharge sales outreach here 👇🏽
3. We launched the Thread Summary JavaScript API
Want to build custom logic to notify users of activity in a specific thread? With Cord’s new Thread Summary JavaScript API, you can.
Now it’s quick and easy to trigger live updates and observe a summary of thread-related activity like the number of messages read and unread, the number of users participating in a particular thread, and the number of threads that users have manually resolved.
Learn more here.
4. We added search to our Docs
You might notice something different about our Docs…it now supports search!
As our product surface continues to grow, we want to make it impossibly easy for our customers and curious developers to get their hands on the information they need to start building collaborative features with Cord.
Bonus: It uses OpenAI language models. #ChatGPT. Give it a try now.
5. We launched new Notification components
Notification systems are hard to build, and they’re even harder to build well. But with Cord’s new Notification components (Notification List and Notification List Launcher) developers don’t have to worry about pagination or badging logic. Woohoo!
It’s all automatically wired into Cord’s other components which means as soon as you drop the notification list component on the page - BAM! - it’ll be populated with all the relevant things that have been happening in the product.
And, thanks to our REST API, you can also programmatically add custom notifications that aren’t triggered by a Cord-specific action. It could be a notification about a security update or a task being completed. Whatever makes sense for your product, and your users.
Click here for a more in depth look at these new components.
6. We got SOC 2 certified
We take data privacy and protection seriously. In fact, it’s fundamental to our goal of making software more collaborative. Cord’s infrastructure, products, and features were all built from the ground up with security by design, and our software development processes follow industry best practice.
And now, we have a SOC 2 Type II certification to prove it! 🎉
Learn more about our certification and review our security policy here.
7. We added placeholder components to threads, inbox, and notifications
Last but certainly not least, we updated placeholders across all of our components. Now, you can control the ‘empty state’ (what end-users see when they don’t have any notifications) on threads, inbox, and notifications. A lot of apps use this space for either a feel-good message like “All done!” or a feature introduction text like “Here you’ll see when people @mention you or reply to your messages”.
Here’s an example:
While this may seem like a small change, it makes a big difference. The updated placeholders will make it easier for developers to see if they’ve implemented a particular component correctly, help deliver a consistent UX across all Cord features, and improve discoverability.
If you don’t want placeholders, you can easily turn ‘em off. Learn more here.
Stay in touch
That’s it for this month! Want to learn more about Cord and see if collaboration is right for your product? Book a demo. And if you want to keep up with Cord and our ever-evolving product, follow us on Twitter and LinkedIn.