Email notifications
Invoice Crowd uses its configured email notification paths for supported document and account events.
- Email remains the supported message path
- Templates follow the application workflow
- Delivery still depends on mail configuration
Feature status
SMS and Mobile Message are not currently integrated
Invoice Crowd does not currently include a native Mobile Message, Twilio or general SMS delivery service. Product notifications use the implemented email and in-app paths. A customer may build a separate workflow from supported outbound webhooks, but Invoice Crowd does not claim to send invoice reminders or payment confirmations by text message.
- No native SMS service
- Email notifications remain available
- No Mobile Message partnership claim
Last updated:
What is actually available
Use the communication channels that are actually implemented
This page is an availability notice. It replaces an obsolete integration claim and does not invite users to configure a connection that the application cannot make.
Current notifications
Implemented channels
Customer-facing documents
Clients use the secure document or portal experience to review, approve, download and pay supported documents.
- No SMS is required
- The document holds the current amount
- Payment status stays with the record
What is unavailable
No hidden connector
No native SMS sender
The current codebase has no Mobile Message, Twilio or generic SMS provider service.
- No text-message reminder job
- No SMS credential screen
- No SMS delivery log
No implied partnership
Invoice Crowd does not claim a current commercial or technical integration with Mobile Message.
- No partner logo claim
- No one-click setup
- No delivery guarantee
Possible external workflow
Separate and customer-managed
Outbound webhook events
Selected events can be sent to a webhook receiver you configure. A separate service could use that event, but its SMS behavior is outside Invoice Crowd.
- Outbound events only
- Receiver controls the next step
- Test consent and compliance separately
Respect messaging rules
If you build an external SMS workflow, obtain the required consent and follow the rules that apply to the recipient and sender locations.
- Consent is not inferred
- Local rules vary
- Keep an opt-out process
Current boundary
The honest communication boundary
The current product should be evaluated on its implemented notification, portal and outbound-webhook behavior.
-
Email, not SMS
Supported notification messages use email.
-
No Mobile Message API
There is no current provider client or credential flow.
-
No Twilio service
Invoice Crowd does not currently send through Twilio.
-
No text-message log
The application does not claim SMS delivery evidence.
-
Customer portal
Clients can review supported documents in the portal.
-
Public document view
The document link holds the live balance and available actions.
-
Outbound webhooks
Selected application events can reach a receiver URL.
-
External workflow
Any SMS action after a webhook is a separate customer-managed service.
-
Consent required
Do not infer permission to send texts from an invoice email address or phone number.
-
No speed promise
This page makes no claim that SMS would accelerate payment.
-
No partner claim
Mobile Message is not presented as a current Invoice Crowd integration.
-
Availability may change
A future integration should be documented only after implementation and verification.
Questions
SMS availability, answered
Can Invoice Crowd send SMS reminders?
No native SMS reminder service is present in the current product.
Is Mobile Message integrated with Invoice Crowd?
No. This page records that the former claim is obsolete.
Does Invoice Crowd support Twilio?
No current Twilio integration was found in the implemented application.
What notification channel should I use?
Use the email and in-app or customer-facing document workflows that are configured and implemented for the event you need.
Could an outbound webhook trigger a separate SMS tool?
A customer-managed receiver may be able to act on a supported event, but that downstream SMS service, its consent model and its delivery are outside Invoice Crowd.
Why is the old URL still here?
Keeping a candid noindexed availability page prevents bookmarks and old links from landing on a false feature claim.
Keep client communication on supported paths
Use Invoice Crowd email, public-document and portal workflows, or design a separately verified webhook workflow without presenting it as native SMS.
- No false SMS claim
- No invented provider partnership
- External workflows remain clearly separate