{"id":828,"date":"2019-12-13T07:35:13","date_gmt":"2019-12-13T07:35:13","guid":{"rendered":"https:\/\/weburlforclients.com\/gamma\/realintelligence\/?p=828"},"modified":"2019-12-13T07:35:13","modified_gmt":"2019-12-13T07:35:13","slug":"9-usefu-salesforce-process-builder-implementations","status":"publish","type":"post","link":"https:\/\/realintelligence.com\/9-usefu-salesforce-process-builder-implementations\/","title":{"rendered":"9 Usefu Salesforce Process Builder Implementations"},"content":{"rendered":"\n<h2>1. Add Lookup field to Opportunity Contact Role<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Sales Cloud (combination of Process Builder and Flow)<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Opportunity, Opportunity Contact Roles<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>We have a client that uses Contact Roles for Opportunities in Salesforce, mostly to manage their Pardot marketing and create cross-selling reports. Contact Roles allow salespeople to associate multiple contacts to an opportunity. However, you cannot require a salesperson to add a Contact Role to an Opportunity, which unfortunately means this data is not captured.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>To resolve this, we created a process builder rule that requires a Lookup field to dynamically populate Contact Roles. A Lookup field creates a lookup relationship between two objects (i.e. Opportunity and Contact Role), creating a one-to-many relationship. By requiring this field, it ensures there can be many contacts for a given opportunity. Likewise, it ensures sales teams are adding contacts to every opportunity, providing more accurate data to sales, marketing, and strategy teams.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Set up a new validation rule.<\/strong>&nbsp;Create a new validation rule by entering a rule name, description, condition formula, and error message from the Validation Rules section in Salesforce. Here\u2019s what we used:<\/p>\n\n\n\n<ul><li>Rule Name: Require_Lookup_Contact_Rules<\/li><li>Description: Validates that the Contact Role cannot be NULL at a certain stage in an opportunity.<\/li><li>Condition Formula: Probability &gt; 0.74 &amp;&amp; Primary_Contact__c = NULL<\/li><li>Error Message: Lookup field cannot be left blank.<\/li><\/ul>\n\n\n\n<p><strong>2. Create the process builder.<\/strong>&nbsp;Configure the process builder to fire when the custom&nbsp;<em>Primary_Contact__c<\/em>&nbsp;field is changed. When a change is made, the process builder will then carry the&nbsp;<em>ContactId<\/em>&nbsp;into the flow. From there, the flow does a Lookup with the&nbsp;<em>ContactId<\/em>&nbsp;to store information as a variable where it will check if the OCR is NULL to either create an Opportunity Contact Role (yes) or update the existing Opportunity Contact Role (no).<\/p>\n\n\n\n<h2>2. Schedule contact reminders and update an opportunity when a connect is made<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Sales Cloud<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Opportunity, Tasks\/Activities, Reports and Dashboards<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>Our client had a longer than normal sales cycle and needed to automate reminders for the sales reps to follow up on opportunities. Likewise, they also needed a way to report on conversations from attempts (activities) to actual connects\/conversations.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>This process builder rule gives you the ability to accurately track client engagement metrics and determine which stages or processes need improvement or additional review. It also allows you to automate reminders for sales reps so they know when to follow up on accounts that haven\u2019t been touched in awhile.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Add a set of custom checkboxes on Activities:<\/strong><\/p>\n\n\n\n<ul><li>Connected_with_Client__c<\/li><li>Meeting_Scheduled?<\/li><li>Request_for_Proposal?<\/li><li>Follow_Up \u2013 checkbox used to exclude activity\/task from reporting<\/li><\/ul>\n\n\n\n<p><strong>2. Add a customer checkbox on Opportunities:<\/strong><\/p>\n\n\n\n<ul><li>Connected_with_Client__c<\/li><\/ul>\n\n\n\n<p><strong>3. Create the first process builder rule (Schedule Contact Reminders):<\/strong>&nbsp;Configure the process to create a series of tasks when an opportunity is created or edited and the Opportunity checkbox Connected_with_Client __c is false. The initial task should be scheduled right away, then time-delayed actions (follow ups) should be scheduled at 15 days, 30 days, 60 days, 150 days, and 270 days.<\/p>\n\n\n\n<p><strong>4. Create the second process builder rule (Update Opportunity \/ Connected With Client):<\/strong>&nbsp;Configure the process to update the related opportunity\u2019s&nbsp;<em>Connected _with_Client__c<\/em>&nbsp;checkbox to true and remove all future scheduled tasks from the pending flow\u2019s queue if a user checks the&nbsp;<em>Connected _with_Client__c<\/em>&nbsp;checkbox on any of the assigned tasks (or any task they created on their own).<\/p>\n\n\n\n<p><strong>5. Configure sales rep reports.<\/strong>&nbsp;The custom checkboxes added to Activities will drive the reporting metrics that management needs to understand conversions per sales rep, as well as the following:<\/p>\n\n\n\n<ul><li><em>Conversion % for Attempts to Connects<\/em>&nbsp;= # of Connects \/ # of total Activities<\/li><li><em>Conversion % for Connects to Meetings<\/em>&nbsp;= # of Meetings Scheduled \/ # of Connects<\/li><li><em>Conversion % for Meetings to Proposals<\/em>&nbsp;= # of Request for Proposals \/ # of Meetings Scheduled<\/li><li><em>Conversion % for Proposals to Closed Business<\/em>&nbsp;= # of Closed Won Opportunities \/ # of Requests for Proposals<\/li><\/ul>\n\n\n\n<h2>3. Automatically move an opportunity to Closed\/Won when a new client digitally signs<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Sales Cloud&nbsp;<em>(Note: you will need a document generation tool)<\/em><\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Opportunity, Tasks\/Activities, Reports and Dashboards<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>After a salesperson closes a contract with a new client, sometimes they forget to update the opportunity record to Closed\/Won in Salesforce. For companies that live by the motto \u201cif it\u2019s not in Salesforce, then it didn\u2019t happen\u201d, this can cause unnecessary bottlenecks, especially for project teams that rely on this small but important detail to officially kick off projects with new clients.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>We created a process builder rule that automatically updates an opportunity to Closed\/Won once a new client digitally signs their contract. By keeping this data inside Salesforce, everything stays accurate and everyone stays up-to-date \u2014 project teams no longer have to wait on a salesperson to update an opportunity record. Likewise, this process builder rule optimizes the onboarding experience for new clients. As soon as a contract is closed, you can automatically send welcome emails and inform them of next steps. You can also automatically assign tasks to project leads so they know as soon as it\u2019s time to kick off a new project.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Set up document generation for contracts.<\/strong>&nbsp;Select a document generation tool of your choosing (such as&nbsp;<a href=\"https:\/\/getconga.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">Conga<\/a>,&nbsp;<a href=\"https:\/\/www.docusign.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">DocuSign<\/a>,&nbsp;<a href=\"https:\/\/getconga.com\/sales-automation-platform\/\" target=\"_blank\" rel=\"noreferrer noopener\">Octiv<\/a>, or&nbsp;<a href=\"https:\/\/www.hellosign.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">Hello Sign<\/a>), then generate the contract from Salesforce. Send the contract from Salesforce or your document generation tool.<\/p>\n\n\n\n<p><strong>2. Update opportunity record upon digital signature.<\/strong>&nbsp;Once the client digitally signs the contract, configure the document generation tool to automatically update the opportunity record to Closed\/Won.<\/p>\n\n\n\n<p><strong>3. Create the process builder rule (Notify Team of Closed\/Won Opportunity).<\/strong>&nbsp;Configure the process to notify the project team via Chatter Post that an opportunity has been won when an opportunity stage =&nbsp;<em>\u201cClosed\/Won\u201d<\/em>. From there, configure the process to create a new task to follow up with the client and assign it to the project lead or main project contact.<\/p>\n\n\n\n<p><strong>4. Set up email templates.<\/strong>&nbsp;Take the process builder rule one step further by setting up email templates that automatically send new clients an introductory email X minutes after the contract is digitally signed. This is a great way to add a personal touch and set project expectations.<\/p>\n\n\n\n<h2>4. Auto-update and standardize opportunity names<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Sales Cloud<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Opportunity<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>Our client had a variety of products for different types of advertising space across multiple types of media (i.e. print magazines, weekly newsletters, event pamphlets, and more). However, their product list was pretty fixed \u2014 it didn\u2019t need to change often, but it did need to be identified by type of media, year, ad size, and month of ad run. Products and price books were too complex for what they needed.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>This process builder rule keeps things simple by allowing you to use picklist values directly off the opportunity object. It not only simplifies reporting, but standardizes Opportunity Names, allowing you to easily identify what \u201cproduct\u201d an opportunity represents. Likewise, you can see what company every product belongs to in both the reporting and list view.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Create picklists on the opportunity.<\/strong>&nbsp;Determine what values are required to identify products. In this example, our client needed 4 picklists:&nbsp;<em>Type of Media<\/em>,&nbsp;<em>Year<\/em>,&nbsp;<em>Ad Size<\/em>, and&nbsp;<em>Month of Ad Run<\/em>&nbsp;(with&nbsp;<em>Ad Size<\/em>&nbsp;being dependent on&nbsp;<em>Type of Media<\/em>).<\/p>\n\n\n\n<p><strong>2. Create the process builder rule (Update Opportunity Name).<\/strong>&nbsp;Configure the process to update the Opportunity name with a standardized formula, e.g.&nbsp;<em>Account Name + Type of Media + Month + Ad Size + Year<\/em>&nbsp;when a record is created\/edited. To concatenate picklist values with spaces for better readability, use&nbsp;<em>&amp; \u201c \u201c &amp; TEXT(field.name__c)<\/em>&nbsp;in the formula.<\/p>\n\n\n\n<h3><strong>FOR SERVICE REPS<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/i1.wp.com\/galvintech.com\/wp-content\/uploads\/2019\/01\/service-reps-process-builder-rules.jpg?ssl=1\"><img loading=\"lazy\" width=\"1024\" height=\"683\" src=\"https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/service-reps-process-builder-rules.jpg\" alt=\"\" class=\"wp-image-830\" srcset=\"https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/service-reps-process-builder-rules.jpg 1024w, https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/service-reps-process-builder-rules-300x200.jpg 300w, https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/service-reps-process-builder-rules-768x512.jpg 768w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<h2>5. Automate milestone completion of incoming emails<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Service Cloud, Omni Channel, Email to Case<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Case, Email, Milestones, Service Level Agreements (SLAs)<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>Our client, a service call center, wanted to ensure that every customer email\/case was responded to within 8 business hours.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>To resolve this, we created a process builder rule that generates new milestones for every incoming and outgoing email\/case. As service reps respond to emails, milestones are completed and metrics, such as average response time and case close time, are captured. This visibility into service rep performance creates accountability \u2014 management can quickly see how many emails a service rep is (or isn\u2019t) responding to. By implementing this process builder rule for our field service clients, they have been able to drastically reduce the overall response time to no more than&nbsp;<em>3 hours!<\/em><\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Add custom fields:<\/strong><\/p>\n\n\n\n<ul><li># of Unread Emails<\/li><li># of Email Responses<\/li><\/ul>\n\n\n\n<p><strong>2. Manage incoming emails:<\/strong><\/p>\n\n\n\n<ul><li>Assign the status of&nbsp;<em>Unread<\/em>&nbsp;to every new email.<\/li><li>Configure the process (Email Milestone Completion) to update the custom field&nbsp;<em># of Unread Emails<\/em>&nbsp;by using the formula (Unread_Emails__c+1). This essentially raises the count by 1 for each incoming email.<\/li><li>Whenever&nbsp;<em>Unread Emails<\/em>&nbsp;has a higher count than&nbsp;<em>Email Responses<\/em>, configure the SLA to create a new milestone.<\/li><li>Tag the new milestone with the record ID for the incoming email, so every milestone is linked with its corresponding incoming email.<\/li><\/ul>\n\n\n\n<p><strong>3. Manage outgoing emails:<\/strong><\/p>\n\n\n\n<ul><li>Assign the status of&nbsp;<em>Responded<\/em>&nbsp;when an email is responded to.<\/li><li>Configure the process (Email Milestone Completion) to update the custom field&nbsp;<em># of Email Responses<\/em>&nbsp;with the formula (Email_Responses__c+1).<\/li><li>When the status of an email changes to&nbsp;<em>Responded<\/em>, configure the process builder rule to close the milestone and stamp it with the current date and time.<\/li><\/ul>\n\n\n\n<h2>6. Notify customers of service appointments via email and SMS<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Field Service Lightning, Service Cloud<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Service Appointment, Work Order, Account, Email Actions<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>Our client needed a way to automatically send notifications to customers when service appointments are scheduled or rescheduled. Although their IT operations were powered by Field Service Lightning via the Salesforce platform, it was lacking this one piece of functionality essential to their success.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>This process builder rule automates email and SMS (text) notifications, notifying customers as soon as their service appointments are scheduled or rescheduled. Likewise, it sends appointment reminders to customers an hour before their scheduled appointment. With this process builder rule in place, our&nbsp;<a href=\"https:\/\/galvintech.com\/portfolio-items\/field-service-lightning-better-way-manage-field-service-operations\/\" target=\"_blank\" rel=\"noreferrer noopener\">field service clients<\/a>&nbsp;have not only experienced fewer missed appointments but greater customer satisfaction.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Send email notifications.<\/strong>&nbsp;Configure the process (Service Appointment Status Changed) to send a custom email alert when the&nbsp;<em>Status<\/em>&nbsp;or&nbsp;<em>Scheduled Time<\/em>&nbsp;field changes on a service appointment.<\/p>\n\n\n\n<p><strong>2. Send SMS notifications.<\/strong>&nbsp;This one is a bit more complicated; we recommend following&nbsp;<a href=\"https:\/\/www.adminhero.com\/send-text-alerts-from-salesforce\/\" target=\"_blank\" rel=\"noreferrer noopener\">this tutorial<\/a>&nbsp;to set up SMS notifications in Salesforce. However, the process builder built for email notifications should also work for SMS notifications.<\/p>\n\n\n\n<h3><strong>FOR CLIENTS &amp; CUSTOMERS<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/i2.wp.com\/galvintech.com\/wp-content\/uploads\/2019\/01\/customers-clients-process-builder-rules.jpg?ssl=1\"><img loading=\"lazy\" width=\"1024\" height=\"683\" src=\"https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/customers-clients-process-builder-rules.jpg\" alt=\"\" class=\"wp-image-829\" srcset=\"https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/customers-clients-process-builder-rules.jpg 1024w, https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/customers-clients-process-builder-rules-300x200.jpg 300w, https:\/\/realintelligence.com\/wp-content\/uploads\/2019\/12\/customers-clients-process-builder-rules-768x512.jpg 768w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<h2>7. Send W-9s to new clients<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Sales Cloud<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Opportunity<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>We often received requests from clients to send them a copy of our W-9, which meant we had to fill out the W-9, create it as a PDF, sign it, then email it back. It was time-consuming for such a simple yet routine task \u2014 there had to be a better way.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>We created a process builder rule that eliminates all the work of sending W-9s to clients. Now, when a client officially becomes a client, our W-9 is one of the first documents they receive. By automating this process, you not only save time, but leave a good first impression with your client\u2019s accounting departments \u2014 they will thank you for the kind and thoughtful gesture.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Create an official W-9.<\/strong>&nbsp;Fill out and sign the document, then save as a PDF.<\/p>\n\n\n\n<p><strong>2. Create an email template.<\/strong>&nbsp;In Salesforce, create a new email template and attach the W-9 to it. Add copy as necessary to give the email that personal touch.<\/p>\n\n\n\n<p><strong>3. Create the process builder rule (Send New Client W-9).<\/strong>&nbsp;Configure the process to automatically update the&nbsp;<em>Type<\/em>&nbsp;field to&nbsp;<em>Client<\/em>&nbsp;when the opportunity enters the&nbsp;<em>Closed\/Won<\/em>&nbsp;stage. When the field changes to&nbsp;<em>Client<\/em>, configure the process to send the email with the attached W-9 to new clients.<\/p>\n\n\n\n<h2>8. Notify internal user and customer of completed\/paid e-commerce order<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Sales Cloud, eCommerce Managed Package, Community Cloud<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Custom Kinetic Growth eCommerce Objects, Contacts, Accounts<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>Our eCommerce client needed a better way to process and ship orders instead of manually looking through stacks of reports to determine which orders needed to be shipped.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>To resolve this, we created a process builder rule that automatically creates and sends an invoice after an order is completed or paid. This invoice is sent to the internal team, allowing them to process and ship customer orders more quickly. Likewise, the invoice is sent to customers to notify them of order, payment, and shipping details.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Grant access to Customer Community.<\/strong>&nbsp;Expose the eCommerce managed package through the Customer Community to grant access to both community members and unauthenticated users.<\/p>\n\n\n\n<p><strong>2. Create the invoice.<\/strong>&nbsp;Design a Visualforce email template that contains all the pertinent information, including customer name, shipping address, billing information, order details, and payment information.<\/p>\n\n\n\n<p><strong>3. Create the process builder rule (Send Order Invoice).<\/strong>&nbsp;Configure the process to send the email to the customer and internal team once the order is moved to a status of&nbsp;<em>Paid<\/em>. This can be automated upon credit card processing with the managed package and custom eCommerce object.<\/p>\n\n\n\n<h2>9. Auto-generate quotes<\/h2>\n\n\n\n<h4><strong>Products:<\/strong><\/h4>\n\n\n\n<p>Sales Cloud<\/p>\n\n\n\n<h4><strong>Objects:<\/strong><\/h4>\n\n\n\n<p>Quotes<\/p>\n\n\n\n<h4><strong>Problem:<\/strong><\/h4>\n\n\n\n<p>Our quoting structure is defined by Terms and Bandwidths \u2014 outside of one term (Terms and Service), our Quote records in Salesforce generally stay the same. However, we often receive requests from clients to see anywhere from 4 to 16 quotes for a single opportunity. Our sales team needed a way to quickly generate quotes to respond to these requests.<\/p>\n\n\n\n<h4><strong>Solution:<\/strong><\/h4>\n\n\n\n<p>We created a process builder that allows our sales team to select up to 4 Terms and 4 Bandwidths for a given Opportunity in Salesforce, generating up to 16 quotes at a time. It also captures these quotes to the Opportunity, allowing us to keep everything inside of Salesforce. We not only respond to client requests more quickly, but do so with little to no data entry.<\/p>\n\n\n\n<p>Here\u2019s how we did it:<\/p>\n\n\n\n<p><strong>1. Create the process builder rule.<\/strong>&nbsp;Set up four fields for&nbsp;<em>Terms<\/em>&nbsp;and four fields for&nbsp;<em>Bandwidth<\/em>. Upon selection of the fields, configure the process builder to automatically generate quotes to an Opportunity with relevant data.<br><\/p>\n","protected":false},"excerpt":{"rendered":"<p>1. Add Lookup field to Opportunity Contact Role Products: Sales Cloud (combination of Process Builder and Flow) Objects: Opportunity, Opportunity Contact Roles Problem: We have a client that uses Contact Roles for Opportunities in Salesforce, mostly to manage their Pardot marketing and create cross-selling reports. Contact Roles allow salespeople to associate multiple contacts to an [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":830,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[11],"tags":[],"_links":{"self":[{"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/posts\/828"}],"collection":[{"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/comments?post=828"}],"version-history":[{"count":0,"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/posts\/828\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/media\/830"}],"wp:attachment":[{"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/media?parent=828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/categories?post=828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/realintelligence.com\/wp-json\/wp\/v2\/tags?post=828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}