Keep your user passwords safe by following these tips.
Use a strong password that is difficult for others to guess and avoid birthdays, names, and pet’s names. Be creative: think of a special phrase and use the first letter of each word as your password. Substitute numbers for some words or letters. For example, “I want to see the Pacific Ocean” could become 1W2CtPo
Use more symbols and numbers in passwords. The reality is that longer, more complex logins are harder to breach.
Never write down your password or share it with others.
Never provide your Botdoc account login or password, credit card number, or other personal information via email or to unknown parties.
Note: Botdoc will never ask you for your password.
Exercise caution using public computers (coffee shops, library, airport, hotel): Public web browsers can cache personal data and store login details. Always log off of web sites and clear the browser cache to protect your personal information, passwords, and accounts.
SAFELY DISPOSE OF PERSONAL INFORMATION
Before you dispose of a computer, get rid of all the personal information it stores. Use a wipe utility program to overwrite the entire hard drive.
Before you dispose of a mobile device, check your owner’s manual, the service provider’s website, or the device manufacturer’s website for information on how to delete information permanently, and how to save or transfer information to a new device. Remove the memory or subscriber identity module (SIM) card from a mobile device. Remove the phone book, lists of calls made and received, voicemails, messages sent and received, organizer folders, web search history, and photos.
AVOID PHISHING EMAILS
Don’t open files, click on links, or download programs sent by strangers. Opening a file from someone you don’t know could expose your system to a computer virus or spyware that captures your passwords or other information you type.
READ PRIVACY POLICIES
Yes, they can be long and complex, but they tell you how the site maintains accuracy, access, security, and control of the personal information it collects; how it uses the information, and whether it provides information to third parties.
REPORT ISSUES
System failures, suspected breach, or general incident
If you are experiencing a system failure, suspect some type of technical incident or breach, or have a general issue, please contact us at[email protected]
Suspicious Emails
If you believe you may have received a fake email, forward the entire email – including the header information – to us at:[email protected], then delete it from your mailbox.
Security Incidents/Breach
If you find or suspect a security incident, please report this to us at:[email protected]
Security is part us, and part you. That’s why we’ve developed best practices for securing your Botdoc-powered applications.
Data Encryption
Files are encrypted in transit (only strong cipher suites) and at rest (AES-256).
Authentication
Two-factor authentication with RSA, SecurID or a digital certificate as well as Active Directory integration.
Network Security
Auto Scaling Firewalls, DDoS Protection, traffic filtering and penetration tests.
Access Controls
Access rights, permissions, and ethical walls based on users and groups.
ISO 27002:2013 & ISO/IEC 27017:2015
Botdoc is ISO27002:2013 certified through MS Azure. This is the highest level of global information security assurance available today, and provides customers assurance that Botdoc meets stringent international standards on security. ISO/IEC 27017:2015 certification, an international standard that aligns with and complements the ISO/IEC 27002:2013 with an emphasis on cloud-specific threats and risks.
Application Security
Static and dynamic application scans, comprehensive logging, and adherence to programming best practices (OWASP Top Ten, etc).
Service Organization Controls (SOC)
Annual Type 2 SOC 2 and SOC 2+ audits based on standards set by the AICPA.
PCI DSS
Botdoc maintains compliance with the current version of the PCI Data Security Standard (DSS) to ensure safe and secure handling of credit card holder information. As overseen by the Payment Card Industry Security Standards Council (PCI SSC), Botdoc places stringent controls around cardholder data as both a service provider and merchant.
HIPAA Compliant
Full compliance with the Health Insurance Portability and Accountability Act of 1996 for privacy, security, and breach notification rules for data storage.
Data Privacy Framework Certified
Botdoc complies with the EU-U.S. Data Privacy Framework, the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. Data Privacy Framework (Swiss-U.S. DPF) as set forth by the U.S. Department of Commerce regarding the legal basis for the movement of data from the European Union and Switzerland to the United States.
FERPA Compliant
Compliant with the US Department of Education regarding data privacy, confidentiality, and security practices related to student-level longitudinal data systems and other uses of student data.
GDPR Compliant
Compliant with processing and holding the personal data of subjects residing in the EU.
GLBA
The Gramm-Leach-Bliley Act (GLB Act or GLBA) is the United States federal law that makes it mandatory for the financial institutions to share their methodology to protect the customers’ financial information. Botdoc follows all safeguard rule requirements and practices to ensure functioning in compliance with standards at all times.
FTC Safeguards Rule
Compliant with the FTC Safeguards Rule that requires non-banking financial institutions (Automotive dealerships) to manage and encrypt customer data at rest and in transit.
Updates and Alerts
Routine maintenance, new features, fixes, updates and other important announcements!
(For best results please clear your browser history/cache after updates)
On Sunday Dec 22, 2024 at 2:00am MST there will be a scheduled service update to Botdoc API Sandbox. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
700Credit Integration
UI/UX fix on P2 Push back button. Too many files would overlay the P2 back button.
Improved P2 Pull File Tags functionality. Added the ability to define required tags
Affected Product/Service: Botdoc API Sandbox only
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
On Sunday Nov 3, 2024 at 2:00am MST there will be a scheduled service update to Botdoc API Sandbox. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Added a new attribute to the Acuant object “use_auto_capture” in order to disable / enable the auto capture on an ID scan
Fixed UI/UX issue when a P2 Push has too many files in it, the files are no longer scrolling behind the back button
Added a Payment Feature to the P2 Container
Added a refresh button on the Domain Feature allows to check any DNS again for a given domain
Affected Product/Service: Botdoc API Sandbox only
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
Botdoc is experiencing login latency and connection issues on the Botdoc NOW product.
Our IT team is working diligently to resolve this issue quickly, we will have more information for to you once resolved. We appreciate your patience and understanding.
On Sunday September 29, 2024 at 2am MST there will be scheduled downtime to enhancements to our Botdoc Now product This planned outage will take approximately 1 hour to perform. We appreciate your patience during this time.
Introducing our NEWEST Feature!
Team Even logs – Admins and Owners of a team can now find the metadata/history of who invited or deleted users, when an account was created as well as when an admin action was performed.
New Push status – Users can now view additional new statuses (inside the details push page)
sent & active
open & active
partial delivered & Active
fully delivered & Active
Add Support Iconon the P2 dashboard – takes you to training videos as well as FAQ’s
Security updates
Bug fixes
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received feedback from our customers that this functionality would be extremely beneficial. Our team is excited to be able to bring this feature to our users. This update makes it even easier for the secure transportation of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
Our SMS servicer (Twilio) is currently experiencing delivery delays when sending messages . This is causing SMS delays from our platform with certain carriers.
Twilio continues to work on the issues and we will have more information to you once resolved. We appreciate your patience and understanding.
On Sunday July 28 2024 @ 2am MST, there will be a scheduled service update/new feature to Botdoc API. We anticipate this planned update will take approximately 1 hr. to perform.
On August 31 Azure will be retiring a few services that will cause a required DNS update for our API users that utilize the Custom Domain Feature on their accounts.
We have created a new Feature for the Custom Domain, improving its functionality and ease of use. However, customers will require to update their DNS names accordingly to continue working properly (point your CNAMEs to a new IP address).
Once the deployment is sent to our Production environment on July 28, 2024, your Custom Domains will still function however, the update on your DNS should take place immediately.
Any existing domain in your account will be automatically created on the new Feature that is being put in place, however there are a few scenarios where this may not happen (expired/invalid certificates, domains that are no longer valid, etc). That will still require you to update your DNS records, as we are just creating the necessary configurations from our side.
We do encourage our customers once this is deployment to the Production; you will need to check your customer domains if they are defined as required. The functionality of the Custom Domain itself remains the same with a few upgrades, those are:
Ability to use Let’s Encrypt certificates. That is an open-source project where SSL certificates are automatically generated and renewed every 3 months as long the DNS records are valid
Create certificate buckets. This allow for custom certificates to be used and associated with domain, it eases the update of certificates when there are many domains that utilizes the same certificate
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of July 21, 2024)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact
to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
On Sunday July 21 2024 @ 2am MST, there will be a scheduled service update/new feature to Botdoc Sandbox API. We anticipate this planned update will take approximately 1 hr. to perform.
On August 31 Azure will be retiring a few services that will cause a required DNS updatefor our API users that utilize the Custom Domain Feature on their accounts.
We have created a new Feature for the Custom Domain, improving its functionality and ease of use. However, customers will require to update their DNS names accordingly to continue working properly (point your CNAMEs to a new IP address).
Once the deployment is sent to our Production environment on July 28, 2024, your Custom Domains will still function however, the update on your DNS should take place immediately.
Any existing domain in your account will be automatically created on the new Feature that is being put in place, however there are a few scenarios where this may not happen (expired/invalid certificates, domains that are no longer valid, etc). That will still require you to update your DNS records, as we are just creating the necessary configurations from our side.
We do encourage our customers once this is deployment to the Production; you will need to check your customer domains if they are defined as required. The functionality of the Custom Domain itself remains the same with a few upgrades, those are:
Ability to use Let’s Encrypt certificates. That is an open-source project where SSL certificates are automatically generated and renewed every 3 months as long the DNS records are valid
Create certificate buckets. This allow for custom certificates to be used and associated with domain, it eases the update of certificates when there are many domains that utilizes the same certificate
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
We had initially anticipated having our newest feature “SSO” to you yesterday, Sunday June 9, 2024 but due to a brief delay and other urgent priorities, we will need a few extra days for this release.
We will send additional updates this week.
Single Sign-On (SSO) – This feature will permit a user to one set of login credentials (like using the credentials to your company email), reducing all user application logins to one login for greater security and convenience.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday June 9, 2024 at 2am MST there will be scheduled downtime to enhancements to our Botdoc Now product This planned outage will take approximately 1 hour to perform. We appreciate your patience during this time.
Introducing our NEWEST Feature!
Single Sign-On (SSO) – This feature will permit a user to one set of login credentials (like using the credentials to your company email), reducing all user application logins to one login for greater security and convenience.
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received feedback from our customers that this functionality would be extremely beneficial. Our team is excited to be able to bring this feature to our users. This update makes it even easier for the secure transportation of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday June 2, 2024 at 2am MST there will be scheduled downtime to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
Ability to edit the Internal Notes on Push or completed Pull “View” page
P2 PUSH – tells who download the files
P2 – Ability to download all files as zip
P2 – Ability to Print (you can now skip the download step, then print)
P1/P2 – You can now Bulk Delete contacts
P1/P2 – Ability to choose P1 or P2 as your default dashboard when logging in
Ability to download non-standard (such as .heic) image format files as PNG
Expire Notification (to customers) 24hrs before a Pull or Push is about to expire
Organizational changes/updates to permission settings
Ability to mark conversations as Private upon creation
Private conversations do not show up in “My ORG” view
Bug fixes and quality of life improvements
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
Enhancing Our Botdoc API With New Features and Capabilities
Planned Maintenance for May 12th, 2024
Hello API Developers,
On Sunday May 12, 2024 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Ability to enable or disable the Acuant Auto Capture. Added new atrribute to Acuant object: use_auto_capture
Ability to reply to a Message inside a P2 Container. Added two new attributes to Message object (enable_reply and force_reply_first). The attributre force_reply_first will disable the general chat while the user does not reply to the Message.
Added new attribute to MessageReply object (reply_to). Foreign Key to the Message object this reply is for.
Ability to define “tags” inside a P2 Pull. Allows the integrator user to define the desired files he/she would like to collect inside the P2-Pull (such as Drivers License, Bank Statements etc)
Added a new endpoint for P2 Pushes that allows users to append Raw Binaries files to a P2 Push
Added new configuration that allows users to change the behavior of the TFA screen page, swamping the 6 text inputs with a single input text
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of May 3, 2024)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We apologize for any inconvenience this may cause and appreciate your patience. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/or [email protected]
Botdoc will have a new update running in our SANDBOX environment TOMORROW May 3, 2024 @ 3am MST!
This update will hit our production servers Sunday May 12, 2024 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
Ability to enable or disable the Acuant Auto Capture. Added new atrribute to Acuant object: use_auto_capture
Ability to reply to a Message inside a P2 Container. Added two new attributes to Message object (enable_reply and force_reply_first). The attributre force_reply_first will disable the general chat while the user does not reply to the Message.
Added new attribute to MessageReply object (reply_to). Foreign Key to the Message object this reply is for.
Ability to define “tags” inside a P2 Pull. Allows the integrator user to define the desired files he/she would like to collect inside the P2-Pull (such as Drivers License, Bank Statements etc)
Added a new endpoint for P2 Pushes that allows users to append Raw Binaries files to a P2 Push
Added new configuration that allows users to change the behavior of the TFA screen page, swamping the 6 text inputs with a single input text
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
Botdoc will have a new update running in our SANDBOX environment SUNDAY March 31, 2024 @ 3am MST!
This update will hit our production servers estimated Sunday April 7, 2024 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
Allow users to provide a custom transport method on the send_notificaiton endpoint, so users can also use a different one when required
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
On Sunday March 3, 2024 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Ability to enable or disable the Acuant Auto Capture. Added new atrribute to Acuant object: use_auto_capture
Ability to reply to a Message inside a P2 Container. Added two new attributes to Message object (enable_reply and force_reply_first). The attributre force_reply_first will disable the general chat while the user does not reply to the Message.
Added new attribute to MessageReply object (reply_to). Foreign Key to the Message object this reply is for.
Ability to define “tags” inside a P2 Pull. Allows the integrator user to define the desired files he/she would like to collect inside the P2-Pull (such as Driver’s License, Bank Statements etc)
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of Feb 25 2024)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
On Sunday February 25, 2024 we deployed some new features.
CLICK on the picture below to view an interactive demo of these updates.
Allow custom domain users, to login into their custom domains via app.botdoc.io
Add language on Dashboard that sending “as Queue” is Optional
(DR) Direct Request Improvement – Ignore 2-Factor if logged in – If a user is logged in and receives a PUSH from another verified user, and that request is linked via the “Direct Request”, feature will ignore the 2fa even if it’s enabled.
Add Badge/Count number of pending actions on the queue tab
Bug fixes to Refresh SMTP oAuth token (Office365 and Google)
P1/P2 Custom Fields Improvements
P2 ID Capture – Add expiration date countdown inside the feature
P2 Personal URL Automation (Magic Wand) page fixes
P2 Contact Search and filtering fixes
P2 Archive/unarchive fixes
Note: Features and updates are no longer supported by Internet Explorer
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
Botdoc will have a new update running in our SANDBOX environment SUNDAY February 25, 2024 @ 3am MST!
This update will hit our production servers estimated Sunday March 3, 2024 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
Ability to enable or disable the Acuant Auto Capture. Added new atrribute to Acuant object: use_auto_capture
Ability to reply to a Message inside a P2 Container. Added two new attributes to Message object (enable_reply and force_reply_first). The attributre force_reply_first will disable the general chat while the user does not reply to the Message.
Added new attribute to MessageReply object (reply_to). Foreign Key to the Message object this reply is for.
Ability to define “tags” inside a P2 Pull. Allows the integrator user to define the desired files he/she would like to collect inside the P2-Pull (such as Driver’s License, Bank Statements etc)
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
On Sunday February 25, 2024 at 2am MST there will be scheduled downtime to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
Allow custom domain users, to login into their custom links via app.botdoc.io
Add language on Dashboard that sending “as Queue” is Optional
(DR) Direct Request Improvement – Ignore 2-Factor if logged in – If a user is logged in and receives a PUSH from another verified user, and that request is linked via the “Direct Request”, feature will ignore the 2fa even if it’s enabled.
Add Badge/Count number of pending actions on the queue tab
Bug fixes to Refresh SMTP oAuth token (Office365 and Google)
P1/P2 add Custom Variables Improvement
P2 ID Capture – Add expiration date countdown inside the feature
P2 SMD Links – Magic wand/link, fixes
P2 Contact Search and filtering fixes
P2 Archive/unarchive fixes
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
Botdoc will have a new update running in our SANDBOX environment SUNDAY December 17, 2023 @ 3am MST!
This update will hit our production servers estimated Sunday January 7, 2024 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
Add ability to define a default Email Subject on Email Templates
Added new endpoint to create a Container with all it’s relationships with a single call
Added “Tag” feature to P2-Pull. When enabled, the “ADD FILE” button on a P2-Pull will become a dropdown button and each file sent using one of the Tags will be tagged as that respectived tag.
Added ability to create Pull and it’s related entities (PullTag) in a single call
Added a new configuration to automatically cast the attribute name of a PullFile once the user sends. The casting will keep only the following characters when enabled:
Characters from A-Z (lower and upper case)
Numbers
Underscores
Dashes
Dots
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
When using SMTP and P2, you will need to add another IP to the allowlist of your IP addresses on the Email server to prevent delays in email-generated requests. The new IP is: 52.154.221.72.
In addition, please note that the complete list of IP addresses that should be added to your allowlist is as follows:
52.154.221.72, 52.165.168.40, 52.165.227.9, 52.165.224.93, 13.89.185.131, 13.89.186.120, 13.89.191.30, 13.89.185.138, 52.173.147.98
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected].
On Sunday October 8, 2023 we deployed some new features.
CLICK on the picture below to view an interactive demo of these updates.
User to User “Direct Requests”. You can now send requests (Pushes or Pulls) to a confirmed Botdoc user and that user will receive a notification directly inside their Botdoc dashboard that a file is either waiting to download or needs to be uploaded.
The Default Email notification template is getting a new look. The email that a recipient receives when they get a Pull or Push request will now be more defined.
Users can now collect a Transcript of the P2 container. Chat history, features etc
Misc Bug fixes on the P1 Queue timeline view and SMTP configurations.
Note: Features and updates are no longer supported by Internet Explorer
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday October 8, 2023 at 2am MST there will be scheduled downtime to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
User to User “Direct Requests”. You can now send requests (Pushes or Pulls) to a confirmed Botdoc user and that user will receive a notification directly inside their Botdoc dashboard that a file is either waiting to download or needs to be uploaded.
The Default Email notification template is getting a new look. The email that a recipient receives when they get a Pull or Push request will now be more defined.
Users can now collect a Transcript of the P2 container. Chat history, features etc
Misc Bug fixes on the P1 Queue timeline view and SMTP configurations.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday August 27, 2023 at 2am MST there will be scheduled downtime to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
Dealership short code automation flow has a verbiage change:
Current flow:
Prompt #1: Thank you for accessing “dealerships” secure portal. To access your secure account, please respond to this message by providing your first and last name.
Prompt #2: Thank you for providing your name. Please tap the link below to upload your documents.
New flow:
Prompt #1: Thank you for accessing “dealerships” secure portal.
Prompt #2: What is your first and last name?
Prompt #3: Thank you. Please tap the link below to upload your documents.
P2 My View & Organization View searching and filter updates – search by “my conversations”, “Queues”, and “Users”
P2 My View & Organization view filter by remote users is now alphabetical.
Pre-Select Queues when sending user invites – Owners/Admins have the option of pre-selecting a queue or multiple queues when sending a user invites.
Duplicated contacts have been mitigated.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday July 9, 2023 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
P2 Conversations: Downloading documents – you can now visually see on the left conversations navigation toolbar and inside the conversations container how many documents are pending download via a download icon. You can also verify how many times a document was downloaded and by what user inside the conversation details.
P2 Conversation Filter: You can now filter any conversation that still has documents needing to be Downloaded. (Filter by: Download pending, Archived or Favorites)
Ability to pre-select a Queue in Team invites. A team admin can now invite the user, then pre-select the queues this user is assigned to. When the user creates their account, it will automatically assign the queue to this user vs you manually adding the user to the queue.
P2 Conversations: Unarchive a conversation automatically when and if a customer interacts or re-engages with an expired conversation.
P2 Conversations: Organization users now have the ability to see all Teams inside the P2 Conversations as well as set up remote users for all their teams.
When creating a Queue, we are now defaulting you as a user to that queue (so you don’t forget to add yourself to the queue)
Allow organization admins to assign a remote user to a conversations. You have the option to change the remote user based on the fact that multiple salespersons shared this lead but ultimately belongs to one salesperson, or the customer could have come with a remote user via a general queue link vs automation link per the salesperson or the salesperson is terminated.
P1 Queues: Ability to view details of the Push and Pull timeline inside a Queue before you assign to a user or to yourself.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday July 2, 2023 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
P2 Conversations: Downloading documents – you can now visually see on the left conversations navigation toolbar and inside the conversations container how many documents are pending download via a download icon. You can also verify how many times a document was downloaded and by what user inside the conversation details.
P2 Conversation Filter: You can now filter any conversation that still has documents needing to be Downloaded. (Filter by: Download pending, Archived or Favorites)
Ability to pre-select a Queue in Team invites. A team admin can now invite the user, then pre-select the queues this user is assigned to. When the user creates their account, it will automatically assign the queue to this user vs you manually adding the user to the queue.
P2 Conversations: Unarchive a conversation automatically when and if a customer interacts or re-engages with an expired conversation.
P2 Conversations: Organization users now have the ability to see all Teams inside the P2 Conversations as well as set up remote users for all their teams.
When creating a Queue, we are now defaulting you as a user to that queue (so you don’t forget to add yourself to the queue)
Allow organization admins to assign a remote user to a conversations. You have the option to change the remote user based on the fact that multiple salespersons shared this lead but ultimately belongs to one salesperson, or the customer could have come with a remote user via a general queue link vs automation link per the salesperson or the salesperson is terminated.
P1 Queues: Ability to view details of the Push and Pull timeline inside a Queue before you assign to a user or to yourself.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday June 11, 2023 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Updated notifications flows. As of this deployment, all communications with a given Servicer Provider for Email, Sms and Voice will be performed asynchronously.
Add a new endpoint to retrieve Sms and Email events directly from the Servicer. From this endpoint, communication may be performed with the Email/Sms Servicer to retrieve the most recent data on a message which may result in higher response times according to the Servicer availability.
Ability to import and export Automation steps.
Updated Transport Method integration with Google Gmail and Microsoft Office 365.
Added endpoint to paginate entities Message and MessageReply from a single call.
Added integration with new Vendor to send emails, Sendinblue
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of May 28, 2023).
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or [email protected]
Botdoc will have a new update running in our SANDBOX environment SUNDAY May 28, 2023 @ 3am MST!
This update will hit our production servers estimated Sunday June 11 2023 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
Updated notifications flows. As of this deployment, all communications with a given Servicer Provider for Email, Sms and Voice will be performed asynchronously.
Add a new endpoint to retrieve Sms and Email events directly from the Servicer. From this endpoint, communication may be performed with the Email/Sms Servicer to retrieve the most recent data on a message which may result in higher response times according to the Servicer availability.
Ability to import and export Automation steps.
Updated Transport Method integration with Google Gmail and Microsoft Office 365.
Added endpoint to paginate entities Message and MessageReply from a single call.
Added integration with new Vendor to send emails, Sendinblue
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
At roughly 6PM Mountain time today (Friday 7 April 2023), Botdoc experienced what we believe to be a DDoS attack. Our services were down from roughly 6:10PM MT to 6:25PM MT due to our own efforts to appropriately address the issue and solve it quickly.
Our environment scaled appropriately and we were notified. Internal network measures were taken per our incident response plan.
At roughly 6:35PM MT everything was brought back online 100%. Based one the sequencing of geographic servers some of our customers may have experienced downtime, others may not have.
As of this update, since 6:35PM MT there have been no anomalies, no degradation of service nor any other attempts of attacks. This event has passed and we do not expect any more issues.
Our team is watching this and our services closely and will continue to do so over the coming weeks.
On Sunday April 2, 2023 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
P1 – ability for Team owners to set Two factor login for all users on team (global feature) bug fixes
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
Disruptions of Botdoc NOW product and API Services
Hello Botdoc Users
Our email service (Mailgun) is having intermittent connection issues which is causing some of our clients, who do not have their own SMTP, to experience connection issues.
Mailgun continues to work on the issues and we will have more information to you ASAP. We appreciate your patience and understanding.
*Please implement by 1/18/2023 for Sandbox deploy and 1/22/2023 for Live production deploy!
Hello Botdoc developers,
Botdoc will be adding a few new Public IPs to it’s pool in the API product.
Customers that have strict firewall rules will be required to add the new IPs to the whitelist accordingly.
If you strict the outbound of your network, you will be required to add our additional inbound to your whitelist.
If you do restrict the traffic received from the internet (This would be the Botdoc API Webhooks), you will be required to add our additional outbound IP to your whitelist.
The new IPs are:
– Inbound: 20.62.143.104
– Outbound: 20.246.242.252
On Sunday January 22 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times. Automotive Industry developers: Allow your customers to set a time to test drive or service maintenance. Financial Industry developers: Allow your customers to set a time to discuss investments, tax preparations or any financial related meeting.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of December 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
*Please implement by 1/18/2023 for Sandbox deploy and 1/22/2023 for Live production deploy!
Hello Botdoc developers,
Botdoc will be adding a few new Public IPs to it’s pool in the API product.
Customers that have strict firewall rules will be required to add the new IPs to the whitelist accordingly.
If you strict the outbound of your network, you will be required to add our additional inbound to your whitelist.
If you do restrict the traffic received from the internet (This would be the Botdoc API Webhooks), you will be required to add our additional outbound IP to your whitelist.
The new IPs are:
– Inbound: 20.62.143.104
– Outbound: 20.246.242.252
POSTPONEMENT MESSAGE: The turn of the new year requires a few more technical aspects to be in place before we deploy to production.
We will be sending out a follow up email with more details as of when this patch will hit our production servers. Thanks for the understanding, and Botdoc wishes a great 2023 to everyone!
On Sunday January 8 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times. Automotive Industry developers: Allow your customers to set a time to test drive or service maintenance. Financial Industry developers: Allow your customers to set a time to discuss investments, tax preparations or any financial related meeting.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of December 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
On Sunday January 8 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times. Automotive Industry developers: Allow your customers to set a time to test drive or service maintenance. Financial Industry developers: Allow your customers to set a time to discuss investments, tax preparations or any financial related meeting.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of December 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
Botdoc will have a new update running in our SANDBOX environment TOMORROW December 21, 2022 @ 7am MST!
This update will hit our production servers estimated Sunday January 8 2023 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times.
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
On Sunday November 20, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Sending email out when certificates are about to expire.
Added the ability to set a redirect to after a P2 Container completes.
Add SMS templates ability
Minor visual bug fixes on Secure Session page
Update Acuant, customer can now click to send ID vs automatically sending after customer takes second photo of their Id.
Moving user to the Complete page after a Container is killed.
Added a new entity, LiketimeMeta. This entity holds Container EVent Values that happen during the lifetime of a Container. Check our documentation to read more on the events that are stored currently
Allowing the P2 session to be embeded into iframes
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of November 13, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this: Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Botdoc will have some new updates running in our SANDBOX environment on November 13, 2022 @ 2am MST!
These updates will hit our production servers estimated Sunday November 20, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
Sending email out when certificates are about to expire.
Added the ability to set a redirect to after a P2 Container completes.
Add SMS templates ability
Minor visual bug fixes on Secure Session page
Update Acuant, customer can now click to send ID vs automatically sending after customer takes second photo of their Id.
Moving user to the Complete page after a Container is killed.
Added a new entity, LiketimeMeta. This entity holds Container EVent Values that happen during the lifetime of a Container. Check our documentation to read more on the events that are stored currently (https://sandboxapi.botdoc.io/documentation/#section/Objects/LifetimeMeta). (documention will show on this URL AFTER the sandbox deploy)
Allowing the P2 session to be embeded into iframes
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
On Sunday August 28, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Added assets manager. Allow users to send images in order to use them as assets on their Custom CSS
Added a new Configuration where users can change the behavior of the Features when a Container completes. Currently, any Feature on a pending state is moved to a completed state once the Container itself completes. This configuration allows users to control the state change of the Feature(s) of all Containers in that Apikey, controlling if the Features should transition to a “complete” state or “expired” state.
Added a new Configuration where users can enable or disable HTML tag stripping from the Webhooks Payload data.
Added a “Download All” functionality to P2 Pushes and, PushPull Pushes. When enabled, a “download all” button will appear as the first item in the file list received by an user. This functionality will be disabled on the Push if the size of all files exceeds 30 Megabytes. In this case, the files on that Push must be downloaded individually.
Updated typos in Documentation
Updated Two Factor Authentication page on the Secure Session. We will now display to the user all of its TFA receiving methods on the same page. This will allow users to request the code again through the same page.
Added new CSS classes to Secure Session HTML elements, so users can select different buttons using CSS selectors according to the Feature(s) states of that Container.
Updated the file removal behavior on a Pull. Users were able to remove files only after its upload was complete. Now, users can cancel the upload of the files both on a P2 Pull and PushPull Pull.
Increased valid window of the TFA codes to 600 seconds. Each code sent on the TFA had a valid window of 180 seconds. This means, the user had to input the code in a maximum of 3 minutes, otherwise he/she would get a “wrong code” error. However, emails may delay according to different providers, this window was not large enough in a few scenarios. Now the TFA codes will be valid for approximately 10 minutes. After the first valid code is used, all previous codes sent (if the user sent more than one) are invalidated.
Updated accessibility elements on the Secure Session page
Adde new attributes to Acuant Feature to control the process mode of the IDs and, the authentication sensitivity of the validation
Create a new entity called “LifetimeMeta”. This entity relates directly with the Container and, it will hold custom metadata about the Container and its related Entities during its lifecycle. Check our API docs in order to see all data stored as LifetimeMeta.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of August 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
On Sunday August 21, 2022 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
Adding a searchable subject line column to the Push and Pull details page
Updated the file removal behavior on a Pull. Users were able to remove files only after the upload was complete. Now, users can cancel the upload of the files during upload if needed.
Updates on white-label syncing on the P2
Bug fixes
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
Botdoc will have some new updates running in our SANDBOX environment on August 21, 2022 @ 2am MST!
These updates will hit our production servers estimated Sunday August 28, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
Added assets manager. Allow users to send images in order to use them as assets on their Custom CSS
Added a new Configuration where users can change the behavior of the Features when a Container completes. Currently, any Feature on a pending state is moved to a completed state once the Container itself completes. This configuration allows users to control the state change of the Feature(s) of all Containers in that Apikey, controlling if the Features should transition to a “complete” state or “expired” state.
Added a new Configuration where users can enable or disable HTML tag stripping from the Webhooks Payload data.
Added a “Download All” functionality to P2 Pushes and, PushPull Pushes. When enabled, a “download all” button will appear as the first item in the file list received by an user. This functionality will be disabled on the Push if the size of all files exceeds 30 Megabytes. In this case, the files on that Push must be downloaded individually.
Updated typos in Documentation
Updated Two Factor Authentication page on the Secure Session. We will now display to the user all of its TFA receiving methods on the same page. This will allow users to request the code again through the same page.
Added new CSS classes to Secure Session HTML elements, so users can select different buttons using CSS selectors according to the Feature(s) states of that Container.
Updated the file removal behavior on a Pull. Users were able to remove files only after its upload was complete. Now, users can cancel the upload of the files both on a P2 Pull and PushPull Pull.
Increased valid window of the TFA codes to 600 seconds. Each code sent on the TFA had a valid window of 180 seconds. This means, the user had to input the code in a maximum of 3 minutes, otherwise he/she would get a “wrong code” error. However, emails may delay according to different providers, this window was not large enough in a few scenarios. Now the TFA codes will be valid for approximately 10 minutes. After the first valid code is used, all previous codes sent (if the user sent more than one) are invalidated.
Updated accessibility elements on the Secure Session page
Adde new attributes to Acuant Feature to control the process mode of the IDs and, the authentication sensitivity of the validation
Create a new entity called “LifetimeMeta”. This entity relates directly with the Container and, it will hold custom metadata about the Container and its related Entities during its lifecycle. Check our API docs in order to see all data stored as LifetimeMeta.
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
On Sunday June 26, 2022 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
P2 – Improving Synchronization between NOW prodcut and API (SMTP, CSS and others)
Bug fixes on expired files
Improvement on UX on PULL request pages. Send/Finish button now has animation.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at [email protected]
On Sunday June 12, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
Changed the text “uploading” to “encrypting” on a P2 Pull file status upload
Added ability to define a custom favicon to be used on the Secure Session page
Added ability to define the Page Title on the Secure Session
Added a new attribute to the Recipient entity which tells if that Recipient is online (has the Secure Session page open). Note: It may take up to 5 minutes to have a Recipient transition back to an “offline” state after being marked as online. The online status does not have any delays, as soon the Secure Session is open, the status is updated to online.
When removing Recipient(s) from a P2 session, they will be redirect to a page that says “This session is no longer available”
Added a few new endpoints to the API in order to retrieve data in bulk.
Navbar on a P2 Session updated
Added a NEW Feature, Acuant. With Acuant you will be able to securely collect IDs and, validate them with Acuant. Acuant will ensure its authenticity and, extract all the data via OCR.
Allowance of HTML tags on the Feature Title and Description attributes.
Added ability to enter custom initials for Requesters
Removed previous code related to the previous Secure session version.
Updated the HTTP Status a QR code returns
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of June 3, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
Botdoc will have some new updates running in our SANDBOX environment on June 3, 2022 @ 2am MST!
These updates will hit our production servers estimated Sunday June 12, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
Changed the text “uploading” to “encrypting” on a P2 Pull file status upload
Added ability to define a custom favicon to be used on the Secure Session page
Added ability to define the Page Title on the Secure Session
Added a new attribute to the Recipient entity which tells if that Recipient is online (has the Secure Session page open). Note: It may take up to 5 minutes to have a Recipient transition back to an “offline” state after being marked as online. The online status does not have any delays, as soon the Secure Session is open, the status is updated to online.
When removing Recipient(s) from a P2 session, they will be redirect to a page that says “This session is no longer available”
Added a few new endpoints to the API in order to retrieve data in bulk.
Navbar on a P2 Session updated
Added a NEW Feature, Acuant. With Acuant you will be able to securely collect IDs and, validate them with Acuant. Acuant will ensure its authenticity and, extract all the data via OCR.
Allowance of HTML tags on the Feature Title and Description attributes.
Added ability to enter custom initials for Requesters
Removed previous code related to the previous Secure session version.
Updated the HTTP Status a QR code returns
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
