Have you seen this SMS Text Message demo from awhile back?

Or you can build a custom solution using Twilio:
https://www.acumatica.com/blog/acumatica-twilio-a-hackathon-solution-in-4-hours/

Thank you for your reply. However, this isn’t what exactly what I had in mind.

In both of these examples, it seems the communication is one way and doesn’t allow for a customer to respond. In my dream scenario, I am looking for a two-way communication system via SMS that will log and record each communication as an activity to the business account. Communication that was hasn’t been responded to would show up on a dashboard of sorts on the business account owner.

I think the route with no coding involves something like this: https://www.clicksend.com/us/sms/email-to-sms/

If you want to go the code customization route, then I would recommend creating an extension library that uses Pipedream to communicate with Telnyx for sending and receiving SMS. I haven’t done this using Acumatica, but I have done it using other systems and it works very well (you could use Twilio also, but I prefer Telnyx).

https://telnyx.com/products/programmable-sms
https://pipedream.com/

I think it would be a relatively straightforward customization using these tools. You can use Pipedream to receive webhooks from Telnyx SMS, and then send the data to the Acumatica API using REST. Similarly, replies to the customer can go through an Acumatica webhook to send an SMS to the customer with Pipedream/Telnyx (this might be useful: https://www.acumatica.com/media/2020/07/2020-Virtual-DevCon-Push-Notifications-Webhooks-Final.pdf).

Telnyx also allows you to do other fancy stuff like call your end user and read their text message to them (IVR APIs). We use this for an emergency alert system and its pretty cool.

This is definitely doable, but absent tying into the Acumatica email correspondence functionality, I think it’s going to require some coding.

@rvalentine11 Asgard Alliance is currently working with a VAR to create a full SMS 2-way integration (from CSR to customer and back with a separate phone number for each CSR) for a customer of theirs. It will support all of the features you have lined out.  If you are interested, we could look at your requirements in more details and see where they would fit in our roadmap. We will be using Twilio for this customer but the architecture will be provider independent so it can be used on other SMS platforms.