diff --git a/CHANGELOG.md b/CHANGELOG.md
index eb48d288a7..1be3704dc7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 
 - Do not retry `firebase.messaging.UnregisteredError` exceptions for FCM relay tasks by @joeyorlando ([#3637](https://github.com/grafana/oncall/pull/3637))
+- Decrease outgoing webhook timeouts from 10secs to 4secs by @joeyorlando ([#3639](https://github.com/grafana/oncall/pull/3639))
 
 ### Fixed
 
diff --git a/docs/sources/outgoing-webhooks/_index.md b/docs/sources/outgoing-webhooks/_index.md
index 8469466e3d..70e61de7fb 100644
--- a/docs/sources/outgoing-webhooks/_index.md
+++ b/docs/sources/outgoing-webhooks/_index.md
@@ -13,13 +13,13 @@ weight: 500
 
 # Outgoing Webhooks
 
-> ⚠️ A note about **(Legacy)** webhooks:  Webhooks that were created before version **v1.3.11** are marked as
-> **(Legacy)**.  Do not worry! They are still connected to their respective escalation chains and will continue to to
+> ⚠️ A note about **(Legacy)** webhooks: Webhooks that were created before version **v1.3.11** are marked as
+> **(Legacy)**. Do not worry! They are still connected to their respective escalation chains and will continue to to
 > execute as they always have.
 > <br/><br/>
 > The **(Legacy)** webhook is no longer editable due to changes to the internal representation. If you need to edit it
-> you must use the `Make a copy` action in the menu and make your changes there.  This will create the webhook in the
-> new format.  Be sure to change your escalation chains to point to the new copy otherwise it will not be active. The
+> you must use the `Make a copy` action in the menu and make your changes there. This will create the webhook in the
+> new format. Be sure to change your escalation chains to point to the new copy otherwise it will not be active. The
 > **(Legacy)** webhook can then be deleted.
 
 Outgoing webhooks are used by Grafana OnCall to send data to a URL in a flexible way. These webhooks can be
@@ -33,7 +33,7 @@ To create an outgoing webhook navigate to **Outgoing Webhooks** and click **+ Cr
 webhooks can be viewed, edited and deleted. To create the outgoing webhook click **New Outgoing Webhook** and then
 select a preset based on what you want to do. A simple webhook will POST alert group data as a selectable escalation
 step to the specified url. If you require more customization use the advanced webhook which provides all of the
-fields described below.  
+fields described below.
 
 ### Outgoing webhook fields
 
@@ -63,7 +63,7 @@ Controls whether the outgoing webhook will trigger or is ignored.
 
 #### Assign to Team
 
-Sets which team owns the outgoing webhook for filtering and visibility.  
+Sets which team owns the outgoing webhook for filtering and visibility.
 This setting does not restrict outgoing webhook execution to events from the selected team.
 
 | Required | [Template Accepted](#outgoing-webhook-templates) | Default Value |
@@ -111,6 +111,9 @@ If no integrations are selected the outgoing webhook will trigger for any integr
 
 The destination URL the outgoing webhook will make a request to. This must be a FQDN.
 
+> ⚠️ **Note** the destination server must respond back within 4 seconds or it will result in a timeout
+> (this can be seen in the "Response Body" under the "Last Run" section)
+
 | Required | [Template Accepted](#outgoing-webhook-templates) | Default Value |
 | :------: | :----------------------------------------------: | :-----------: |
 |    ✔️    |                        ✔️                        |    _Empty_    |
@@ -467,7 +470,7 @@ otherwise it will only display the value. Fields which are not used are not show
 
 ### Using trigger template field
 
-The [trigger template field](#trigger-type) can be used to provide control over whether a webhook will execute.  
+The [trigger template field](#trigger-type) can be used to provide control over whether a webhook will execute.
 This is useful in situations where many different kinds of alerts are going to the same integration but only some of
 them should call the webhook. To accomplish this the trigger template field can contain a template that will process
 data from the alert group and evaluate to empty, True or 1 if the webhook should execute, any other values will result
diff --git a/engine/apps/webhooks/tests/test_trigger_webhook.py b/engine/apps/webhooks/tests/test_trigger_webhook.py
index 9cb7857703..ae32ede6c4 100644
--- a/engine/apps/webhooks/tests/test_trigger_webhook.py
+++ b/engine/apps/webhooks/tests/test_trigger_webhook.py
@@ -13,6 +13,8 @@
 from apps.webhooks.tasks.trigger_webhook import NOT_FROM_SELECTED_INTEGRATION
 from settings.base import WEBHOOK_RESPONSE_LIMIT
 
+TIMEOUT = 4
+
 
 class MockResponse:
     def __init__(self, status_code=200, content=None):
@@ -161,7 +163,7 @@ def test_execute_webhook_ok(
     assert mock_requests.post.called
     expected_call = call(
         "https://something/{}/".format(alert_group.public_primary_key),
-        timeout=10,
+        timeout=TIMEOUT,
         headers={"some-header": alert_group.public_primary_key},
         json={"value": alert_group.public_primary_key},
     )
@@ -324,7 +326,7 @@ def test_execute_webhook_ok_forward_all(
     }
     expected_call = call(
         "https://something/{}/".format(alert_group.public_primary_key),
-        timeout=10,
+        timeout=TIMEOUT,
         headers={},
         json=expected_data,
     )
@@ -405,7 +407,7 @@ def test_execute_webhook_using_responses_data(
     expected_data = {"value": "updated"}
     expected_call = call(
         "https://something/third-party-id/",
-        timeout=10,
+        timeout=TIMEOUT,
         headers={},
         json=expected_data,
     )
@@ -547,7 +549,7 @@ def test_response_content_limit(
     assert mock_requests.post.called
     expected_call = call(
         "https://test/",
-        timeout=10,
+        timeout=TIMEOUT,
         headers={},
     )
     assert mock_requests.post.call_args == expected_call
@@ -595,7 +597,7 @@ def test_manually_retried_exceptions(
     # should retry
     execute_webhook(*execute_webhook_args)
 
-    mock_requests.post.assert_called_once_with("https://test/", timeout=10, headers={})
+    mock_requests.post.assert_called_once_with("https://test/", timeout=TIMEOUT, headers={})
     spy_execute_webhook.apply_async.assert_called_once_with((*execute_webhook_args, 1), countdown=10)
 
     mock_requests.reset_mock()
@@ -607,5 +609,5 @@ def test_manually_retried_exceptions(
     except Exception:
         pytest.fail()
 
-    mock_requests.post.assert_called_once_with("https://test/", timeout=10, headers={})
+    mock_requests.post.assert_called_once_with("https://test/", timeout=TIMEOUT, headers={})
     spy_execute_webhook.apply_async.assert_not_called()
diff --git a/engine/apps/webhooks/utils.py b/engine/apps/webhooks/utils.py
index fc8b01be72..8599dd453b 100644
--- a/engine/apps/webhooks/utils.py
+++ b/engine/apps/webhooks/utils.py
@@ -11,7 +11,7 @@
 from apps.schedules.ical_utils import list_users_to_notify_from_ical
 from common.jinja_templater import apply_jinja_template
 
-OUTGOING_WEBHOOK_TIMEOUT = 10
+OUTGOING_WEBHOOK_TIMEOUT = 4
 
 
 class InvalidWebhookUrl(Exception):